Delete dynamic import package

help
1

I deleted dynamic-import and used

meteor remove dynamic-import

This is my packages

meteor-base@1.4.0             # Packages every Meteor app needs to have
mobile-experience@1.1.0       # Packages for a great mobile UX
mongo@1.10.1                   # The database Meteor supports right now

standard-minifier-css@1.7.1   # CSS minifier run for production mode
standard-minifier-js@2.6.0    # JS minifier run for production mode
es5-shim@4.8.0                # ECMAScript 5 compatibility for older browsers
ecmascript@0.14.4              # Enable ECMAScript2015+ syntax in app code
typescript@4.1.2              # Enable TypeScript syntax in .ts and .tsx modules
shell-server@0.5.0            # Server-side component of the `meteor shell` command

static-html             # Define static page content in .html files
apollo                  # Basic Apollo integration for Meteor apps
swydo:graphql           # Import .graphql files

server-render@0.3.1
accounts-password
react-meteor-data
http
less

dburles:mongo-collection-instances
nimble:restivus

ostrio:cookies
mizzao:timesync

I use @loadable/component to dynamically import the library，When I use bundle-visualizer, I see that the dynamic-import package still exists and takes up 117kb,

I did not use the import() method, so does the dynamic-import package have to exist? I have deleted this package. Does it have to exist?

2

It is probably a dependency of another package.
Try the following command to see the dependencies:

meteor list --tree
3

Thank you. I see it
Dependencies are core packages that cannot be deleted, right?

typescript@4.1.2                              
├── babel-compiler@7.6.0 (expanded above)     
├── babel-runtime@1.5.0 (expanded above)      
├── dynamic-import@0.6.0 (expanded above)     
├── ecmascript-runtime@0.7.0 (expanded above) 
├── modules@0.16.0 (expanded above)           
└── promise@0.11.2 (expanded above)
4

It’s all right. It’s just a curiosity. It’s not too big )

5

Also if utilized it could decrease your bundle size for other modules, thus paying for the cost of it’s inclusion.