Closed grgur closed 5 years ago
My thoughts on this is that nothing within gimbal, as it stands right now, is actually scoped to any one thing. The cra
command executes things that would work for any web page. Having something like this would be a great thing to include to also give this command an actual "cra" thing.
I can also see the benefit of the smart detection as you outlined. This one module to support this would have an array of tests and we can add to that array as we need to easily.
I've mentioned to Matt before that I think if there is a failure, we should provide a link to a document (in git so we can update without needing a deployment of gimbal) where we have Modus recommendations on frequent issues per module. What you propose here is in the same area as this and is a start to a programmatic implementation of some recommendations.
Merged in for thresholds of the child file sizes. Will be deployed with next publish.
CRA has deprecated Webpack Bundle Analyzer in favor of Source Map Explorer.
Let's see what we can learn from the bundles and sourcemaps
Stock CRA Output
MoDir Output
lodash
bundled, ormoment.js
bundled with other modules)The one thing we can figure out for CRA but I'm not sure how to detect in other environments without
webpack
stats is the entry point. I think the key factor is web perf is keeping the entry point (app core) light.