Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

meta: add back engines #85

Closed
wants to merge 1 commit into from
Closed

meta: add back engines #85

wants to merge 1 commit into from

Conversation

larsgw
Copy link
Contributor

@larsgw larsgw commented Oct 23, 2018

Add back engine restrictions, as npm 6 is incompatible with node 4 but still tries to update.

See https://npm.community/t/2837
See c6ddb64

Add back engine restrictions, as npm 6 is incompatible with node 4 but 
still tries to update.

See https://npm.community/t/2837
See c6ddb64
@larsgw larsgw requested a review from a team as a code owner October 23, 2018 11:59
@zkat
Copy link
Contributor

zkat commented Nov 13, 2018

We have a separate mechanism for notifying users of incompatibility. I do not consider this to be necessary and, as pointed out, causes pains when testing npm itself.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants