-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package.json node engine >=0.8 might be incorrect #68
Comments
Hey thanks for this. It's a warning that shouldn't be outputted, hence why it is not present in 0.12 despite 0.12 not supporting it anyway. Will work anyway. The fix has already been pushed to the latest typechecker (which now uses the esnextguardian package), the extract-opts package needs to be updated, I'll focus it on my next todo. Currently having some personal matters to attend to this week, so will aim for next week. Cheers. |
Changes for this:
I wish npm actually gave data on their website about which percentage of node version categories (0.8, 0.10, 4, 5) are actually installing your deps. |
/ref #69 |
I've updated extract-opts to once again work on node 0.10, and added explicit tests for 0.10 compat |
Will drop 0.10 support. It will be up to the user to include the babel polyfill for environments less than node 0.12. See bevry/base#20 for details. |
When you're on an older version of node, say 0.10.40, and you load cson:
So one of the subdependencies needs es6. Despite this, it seems like cson works in older nodes, just with an error above.
Not sure what the correct solution is since I'm not the maintainer.
The text was updated successfully, but these errors were encountered: