I don’t think it would cause any issues really, normally I don’t touch the code produced by forge, I just had to dig into it to fix the image upload size this last time but otherwise I just leave it alone.
As far as package size with express, it was my understanding that they tried to combat that with v4 by removing most of the middleware and making it a bit more moduler, right now all packages come in around 2 megs from what I can tell.
I think an approach that could be taken for the build process is why copy everything over to the dev folder each time if nothing has really changed? I think what could make it way faster would be, when saying running
forge run web
is to just copy over the src files to the development directory and start the app. From what I can tell right now is it builds the whole project out again, checking forge modules, deleting the development folder then moving it all over to that folder again. On windows anyhow this is a bit problematic because node at times will hold on to that folder, locking it and the build fails. I have to use a tool called
EMCO UnLock IT
To unlock the development folder so builds will work again, so it would be great to have it simply copy over the src files because 99% of the time I’m not updating the modules in force just my src code. Really it could be extended even further for more granularity to have flags like
forge run web --folder --js
So it would only copy the js folder in src,that would make it way faster than a full rebuild and I would imagine cut back on the API calls each time too.
Sorry for the long response