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
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:
... 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.
The text was updated successfully, but these errors were encountered:
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:
... 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
.The text was updated successfully, but these errors were encountered: