@jack-capable/nx-forge v1.2.0
Nx Forge
Nx plugin for Atlassian Forge that aims to assist in efficient, scalable app development and remove the mental overhead of how to set up a Forge project. Building on top of Nx means shared code can easily be extracted into libraries, and Custom UI can be integrated into the app and dev workflow without having to break with the monorepo structure that Nx provides.
Prerequisites
The following setup procedure assumes you already have a Nx workspace. If you do not, make sure to create one using
npx create-nx-workspace <workspace-name> --preset=apps
You will be asked if you would like to use Nx Cloud or not (either option is fine). Once, the workspace has been created run cd <workspace-name>
.
Finally, make sure your workspace has the following packages (peer dependencies) installed
npm install --save-dev @nx/node
Setting up
Install the plugin
Add the plugin to your Nx workspace using
npm install --save-dev @toolsplus/nx-nx-forge
or
yarn add --dev @toolsplus/nx-nx-forge
Generate a Forge app
Once installed, run the Forge app generator to generate a Forge app.
nx g @toolsplus/nx-nx-forge:app <nx-forge-app-name>
Hint: You can use the
--dry-run
flag to see what will be generated.
Replacing <nx-forge-app-name>
with the name of the app you're wanting to create.
Add a Custom UI module
Forge apps require at least one module before they can be deployed. Let's start with a simple Custom UI module to get started. If you have not yet installed @nx/react
in your workspace call npm i -D @nx/react
. This allows us to generate a React application for our Custom UI:
nx g @nx/react:app <custom-ui-app-name>
Hint: You can use the
--dry-run
flag to see what will be generated.
Replacing <custom-ui-app-name>
with the name of the Custom UI project you're wanting to create.
To get this React app working as a Forge Custom UI update the apps/<custom-ui-app-name>/project.json
file by replacing the baseHref
value in the build options with .
instead of /
(refer to the Forge docs for additional details):
{
"root": "apps/<custom-ui-app-name>",
"sourceRoot": "apps/<custom-ui-app-name>/src",
"projectType": "application",
"targets": {
"build": {
"executor": "@nx/webpack:webpack",
"outputs": ["{options.outputPath}"],
"defaultConfiguration": "production",
"options": {
"compiler": "babel",
"outputPath": "dist/apps/<custom-ui-app-name>",
"index": "apps/<custom-ui-app-name>/src/index.html",
-----> "baseHref": ".",
...
}
},
...
}
}
Wire the Custom UI project with the Forge app project
Back in the Forge app project, open the generated manifest.yml
file and add a Custom UI module and the corresponding resource entry:
modules:
jira:projectPage:
- key: project-page
title: Project page Custom UI
layout: basic
resource: project-page
resolver:
function: resolver
function:
- key: resolver
handler: index.handler
resources:
- key: project-page
path: <custom-ui-app-name>
tunnel:
port: 4200
permissions:
content:
styles:
- 'unsafe-inline'
app:
id: ari:cloud:ecosystem::app/to-be-generated
The most important bit to note here is that the path
property of the project-page
resource should refer to the Custom UI project name from the previous step. This tells the Nx Forge plugin which Nx app project corresponds to the project-page
resource. The plugin will replace this path with the path to the actual Custom UI build artifact during the Forge app build.
Initial build, registration, deployment and installation
Before you can deploy the Forge app it needs to be registered with the Forge platform. To do this, initially build the Forge app using
nx build <nx-forge-app-name>
Once that's finished, run
nx register <nx-forge-app-name>
This will use <nx-forge-app-name>
by default as the app name on the Forge platform. If you would like to use a different name add the app name flag as follows: --appName="My Forge App"
.
Then run
nx deploy <nx-forge-app-name>
to deploy the Forge app to the default development environment.
Finally, install the app in any of your sites with the following command
nx install <nx-forge-app-name> --site <my-atlassian-site.atlassian.net> --product <jira|confluence|compass> --no-interactive
The Forge app is now registered, deployed and installed with the Forge platform.
That's it for the setup steps. You can now generate additional Custom UI resources, generate shared Nx libraries to keep shared app logic and depend on it in one or more Forge apps.
Using the Nx Forge plugin
For any of the plugin targets below append --help
or -h
to explore all available options.
Register
Run nx register <nx-forge-app-name>
to register the Forge app with the Forge platform.
Build
Run nx build <nx-forge-app-name>
to build the project. The build artifacts will be stored in the dist/
directory.
Deploy
Run nx deploy <nx-forge-app-name>
to deploy the project. The build artifacts will be deployed using the Forge CLI deploy command.
Install
Run nx install <nx-forge-app-name>
to install the Forge app. The CLI will prompt for site, product if they are not provided as parameters.
Tunnel (experimental)
Run nx serve <nx-forge-app-name>
to serve the project. This will start the serve
target for all Custom UI projects defined in the app manifest.yml
on their specified tunnel port. After that, it will start a build process in watch mode for the Forge app itself, before ultimately, starting the nx-forge tunnel
process for the Forge app.
Migrate to a newer plugin version
As of plugin version 2.2.0 the plugin ships with migration scripts that allow you to use the nx migrate
to update your workspace to a newer version of nx-forge
.
To update to the latest nx-forge version run the command below and then follow the instructions in the terminal output.
nx migrate @toolsplus/nx-forge@latest
Refer to the Nx migrate docs for more details on how to use nx migrate
.
Further help on how to develop with Nx
Visit the Nx Documentation to learn more.
1 year ago