-
Notifications
You must be signed in to change notification settings - Fork 621
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
no longer working on node 0.12 #161
Comments
You actually don't need IO.js. If you use node though it needs to be version 0.12+, and you need to run it with the The I agree that this should be documented somewhere. |
See also #151 |
a few points to be made here (and in relation to #151)
now this is not a problem for me, and many others, we can simply enable the flag, or just switch to io.js ... but as a principal, I find this flawed to release stable software, but depend on unstable platform functionality (although very usable). I certainly understand the attraction of using ES6 functionality such as generators, and I use it myself, but if I am to release a software package to the public, I would wrap it with babel.js (or similar) and make it compatible with all the supported platform versions. this is more for the community's benefit than own preferences ... if the work is just my own, i'd be on the bleeding edge at every step of course ;) at the end of the day, this is all nothing more than an academic discussion, the software works, and better documentation of the dependency helps. |
Yeah, I kind of agree on your point about unstable software, and I definitely agree that this should be documented somewhere. Regarding the io.js/node convergence, I haven't been following that drama much since the split, but from what I can see now I'm not sure your assessment of io.js as being the "unstable" release of node is correct. (Or maybe I'm just misunderstanding what you were trying to say.) Based on what I read in nodejs/node#2327, it seems like what we currently call io.js is effectively being renamed to "Node.js", and changes from the old Node.js are being merged into that project. Versions 0.12.x and older of Node.js will be from the old Node.js, and new releases will start from v4.0 and be based on io.js plus all the upstream changes from the old Node.js. From an outsider's perspective, this basically means Node.js's next major release will be version 4.0 and will include all the features from io.js and more, and that io.js is deprecated and will receive no new major releases. With that in mind, I think the best course of action for Metalsmith is to simply document the flags and version requirements need for it to run on Node.js, and continue stating that it's compatible with io.js. Then when Node.js 4.0 comes out, update the documentation to state that Metalsmith is compatible with all versions of io.js, Node.js version 4.0+, and Node.js 0.12.x with the |
yep, but since
yup 👍 |
How to use Metalsmith v2 with node.js 0.10 and 0.12 as per metalsmith#161 and metalsmith#151
@ahmadnassri I think this can be closed now. Explained in the readme: https://github.com/segmentio/metalsmith#troubleshooting |
Heh, well that was fast: https://nodejs.org/en/blog/release/v4.0.0/ |
seems like you switched to io.js which is awesome, but there's no note on the website or anywhere in the docs that indicate that io should be used... when I upgraded my dependencies to latest version, it stopped working, till I realized its using generators and needed to switch to io
The text was updated successfully, but these errors were encountered: