Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Engine restriction support with the multi-stage installer #6931

Closed
iarna opened this issue Dec 15, 2014 · 1 comment
Closed

Engine restriction support with the multi-stage installer #6931

iarna opened this issue Dec 15, 2014 · 1 comment
Milestone

Comments

@iarna
Copy link
Contributor

iarna commented Dec 15, 2014

There are two pieces to this:

First, we need to have a tree validator that looks for packages without valid engines and warns or errors (determined by --engine-strict and --force).

Second, the package version selector should enclude engine criteria in its package selector filter, UNLESS the package was specified on the command line and the specifier is *.

@iarna iarna added this to the multi-stage install milestone Dec 15, 2014
@iarna
Copy link
Contributor Author

iarna commented Mar 26, 2015

Closing this as fixed in npm/npm#multi-stage

@iarna iarna closed this as completed Mar 26, 2015
@npm npm locked and limited conversation to collaborators Jun 24, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant