Skip to content
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

[Question] Can node modules that have a binary still be hoisted? #12

Open
shirakaba opened this issue Nov 26, 2020 · 0 comments
Open

[Question] Can node modules that have a binary still be hoisted? #12

shirakaba opened this issue Nov 26, 2020 · 0 comments

Comments

@shirakaba
Copy link
Contributor

shirakaba commented Nov 26, 2020

At this point, my demo app's package.json contains only one dependency that isn't hoisted: @nativescript/webpack.

I'm still amazed though, that this one dependency alone leads to the installation of all these other node modules. Given that any folder that lacks an "alias" arrow – except for the case where the folder is an organisation name – indicates that it wasn't hoisted:

image

... To my understanding, in the general case, Nx can't hoist any devDependency that hosts a binary executable; but is there some kind of advanced (yet safe) workaround for this? Just seems a shame to be carrying nearly 95.2 MB in each of my demo apps's node_modules folders just because of @nativescript/webpack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant