My Meteor 1.8 / React project is using
rc-color-picker on the front-end. I’m using dynamic code-splitting. On the route which imports the color picker tons of other modules are imported, including lots of babel-runtime, core-js and others. Is this normal, or something badly configured with this component or one of its dependencies, or something wrong with my setup?
Here’s 3 out of the 4 pages of modules which are fetched from the
/__meteor__/dynamic-import end-point along with
rc-color-picker on my production server. If I don’t import
rc-color-picker none of these other modules are imported:
I guess this isn’t specifically a Meteor problem, but maybe I’ve got something wrong with my Meteor build process. Any ideas?
I’ve raised a bug here, but no response there yet…
I’m not that familiar with npm modules and their
peerDependencies so I don’t really know where to start tracking down which module is causing this. Any help is greatly appreciated.