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.
At this point, my demo app's
package.jsoncontains 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_modulesfolders just because of@nativescript/webpack.