With version 2.0 the LD-Wizard relies on a separate JavaScript file to load a custom configuration and transformations. This makes recompiling the complete Wizard unnecessary, and removing this step will reduce time spent.
Tough recompiling does come with a few benefits for maintainers of configurations:
Type safety, warning the user about invalid properties, without having to resort to validating the configuration (It's hard to verify the transformation functions as well)
Package management, a user doesn't have to worry about bundling or tree shaking or recompiling
So in order to keep these benefits, we should:
Make it so that the release exposes the build results (JS, CSS and types)
Change the LDWizard script so that it:
Copy the build result
Compile the configuration file (Doesn't have to be webpack) and move it into the out folder
With version 2.0 the LD-Wizard relies on a separate JavaScript file to load a custom configuration and transformations. This makes recompiling the complete Wizard unnecessary, and removing this step will reduce time spent.
Tough recompiling does come with a few benefits for maintainers of configurations:
So in order to keep these benefits, we should: