Hi,
We are running a multi-module Forge app that uses multiple resources, in our current setup each resource is a separate npm module with its own webpack config. Long story short there is a lot of boilerplate and a lot of setup work whenever we want to add a new resource.
I think this could be simplified a bit I’ve already implemented a webpack config with multiple separated entrypoints, each having its own dependency graph. As a build result each forge resource is a separate html file with corresponding js and css files in the same dist/build directory.
Such a setup would simplify things a lot for us, however, there are two blockers in forge.
One is the limitation of forge config that requires resource path to be a directory, ie. currently we cannot specify a specific html file.
Another is forge tunnel which only allows specifying a port, no option to customize url path.
Hence my question, are there any plans to make forge easier to use with large scale multi-module apps? Am I missing something here?