Skip to content

[BUG] gypfile:false no more honored #3341

Open
@adnan-kamili

Description

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

We ship the compiled node addons with our npm package. To prevent npm from trying to build the package on npm install we set "gypfile":false in the package.json. It worked fine up to npm v6.x but doesn't work in npm v7.13.0.

If this is the new default behaviour and "gypfile":false is dropped altogether (like yarn doesn't honour this too), do we have any alternate way to prevent npm from building the package on npm install.

Expected Behavior

npm install should not attempt to rebuild the package when "gypfile":false

Steps To Reproduce

No response

Environment

  • OS: macOS 11.0
  • Node: 16
  • npm: 7.13.0

Metadata

Assignees

No one assigned

    Labels

    Bugthing that needs fixingPriority 2secondary priority issueRelease 7.xwork is associated with a specific npm 7 release

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions