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

Drop node < 4 #358

Merged
merged 1 commit into from
Aug 1, 2016
Merged

Drop node < 4 #358

merged 1 commit into from
Aug 1, 2016

Conversation

hzoo
Copy link
Member

@hzoo hzoo commented Aug 1, 2016

Fixes #323

@@ -29,6 +29,9 @@
},
"author": "Sebastian McKenzie <sebmck@gmail.com>",
"license": "MIT",
"engines": {
"node": ">=4"
Copy link
Member

Choose a reason for hiding this comment

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

Should there be an upper limit placed here? Although it's probably pretty unlikely that a future Node would break this library, we can't know for sure until they're released :)

Copy link
Member

Choose a reason for hiding this comment

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

If a new node version breaks, we have to take action in any case. If it not breaks, then in this case we wouldn't have to do anything, but with limit we would always need to care. So I think it is fine like it is :)

@jamesplease
Copy link
Member

lgtm 👍

@hzoo hzoo merged commit 9fc4e02 into master Aug 1, 2016
@hzoo hzoo deleted the drop-before-node-4 branch August 1, 2016 19:00
nicolo-ribaudo pushed a commit to babel/babel that referenced this pull request Nov 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants