You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, I'm wondering why we are downloading things from npm "again".
Especially in the case of using the usePackageJSON option, after installing the dependencies for a project, all those dependencies are already available in the local file system.
What would it take to just use those files?
Or is there a good reason not to do that?
The text was updated successfully, but these errors were encountered:
Meanwhile we switched to copying files from node modules, which is of course way faster and more reliable.
For that we use some custom field in package.json that points to the file in the the node_modules/package folder, which we nerd to copy, since we need to pick the correct UMD build.
We also have some handling for development mode, where we copy source maps of that file if available and look for unminified/development version of a file and copy that one instead.
Hey there, I'm wondering why we are downloading things from npm "again".
Especially in the case of using the
usePackageJSON
option, after installing the dependencies for a project, all those dependencies are already available in the local file system.What would it take to just use those files?
Or is there a good reason not to do that?
The text was updated successfully, but these errors were encountered: