Replies: 2 comments
-
|
We have released version 3.3.0-beta.2, including a In the next step, we are looking for people to test the After that, we update the application generator to generate applications with a
|
Beta Was this translation helpful? Give feedback.
-
|
The package executor has now been released in version 3.3.0. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
The plugin, in its current form, provides its own build executor. I see two issues with this approach:
These circumstances make it difficult to substitute the build target e.g. with vite or esbuild.
Suggested solution
Split the existing build executor into two targets:
buildandpackage, inspired by the Maven build lifecycle phases.build: This is now a standard build target. The choice is with the user what they would like to use. The application generator provides a set of options that it can configure. However, the user could configure a custom build if they wanted to.package: All existing executor code that's not build-related moves to a package executor. Its goal is to take the built (compiled) code and package it in its distributable format, i.e., whatever the Forge CLI expects. This means it would assemble the Forge app in the output path by copying built Custom UI dependencies (and later maybe also UI Kit 2) and patching the Forge manifest with the path to the actual output directory.Beta Was this translation helpful? Give feedback.
All reactions