-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple modulesDir
s
#32
Comments
Please, this is very important. Especially when working with things such as yarn workspaces now. There are multiple node_modules folders to take into account. |
Looking for a solution to a similar problem. Looks like there's a lot of similar issues about nested/parallel node_modules/ folders: I'm not sure what an accurate summary of the problem would be since there's different use cases. Perhaps "Fix nodeExternals only excluding root node_modules folder"? Assuming my comment nicely cross references all the issues with links, all but one can be closed to avoid confusion. @liady what do you think? |
There was a suggestion in the PR comments above to use multiple calls to node externals however this doesn't necessarily work when a whitelist is used. We were able to find a solution that worked with some tweaks without the need for multiple ModulesDir. The following config works if you have a local package which should be bundled but without it's dependencies:
say the setup is:
Note:
I found it's really helpful to make a diagram of where your modules and their respective node_modules folders are to identify why some dependencies are considered external or not. For example if you also rely on say lodash being available but its only installed in the root, the config above will try to bundle it because it's not in module_a/node_modules so you should be able to make it work with something like
Looks like #56 also duplicates this. |
In version |
In my project i has common
package.json
with common modules and child modules with their specific libs. So formodulesDir
option i need to define bothnode_modules
folders for proper bundling.The text was updated successfully, but these errors were encountered: