Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Open
@shirakaba

Description

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /