Skip to content

Commit

Permalink
#1660: Fix engines syntax in package.json (#1661)
Browse files Browse the repository at this point in the history
  • Loading branch information
ungrim97 committed Jan 7, 2022
1 parent 2f4af99 commit d442ae1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@
"zuul": "^3.12.0"
},
"engines": {
"node": ">=6.4.0 <13|>=14"
"node": ">=6.4.0 <13||>=14"
},
"homepage": "https://github.com/visionmedia/superagent",
"husky": {
Expand Down

5 comments on commit d442ae1

@niftylettuce
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This actually doesn't fix it, it causes another issue, I think our syntax is still wrong

@niftylettuce
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need a space before and after the ||. Testing now.

@niftylettuce
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ungrim97
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@niftylettuce by wrong do you mean it still wouldn't install or that it wouldn't correctly apply the range?

I assume the latter based on your change

@niftylettuce
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ungrim97 Well I think your syntax was right, but eslint didn't parse engines properly so it was giving me an error. The simpler fix was to just do >= 6.4 !13, since all we wanted to do was exclude v13 entirely. This version without the || seemed to pass with eslint. See discussion here mysticatea/eslint-plugin-node#315.

Please sign in to comment.