You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 18, 2019. It is now read-only.
@rictorres - Something to keep in the back of your mind. The move to default es6 module output has begun, it is something you will see more over the coming months & Node v8 LTS isn't too far off.
It's time to get off the older node / IO.js versions & Webpack 1.x. That said, you are in luck! The webpack-cli team is looking for people to test their migration tool which may provide a simplified migration to webpack@latest for your projects.
@d3viant0ne I understand that :)
Most of my personal projects are using Node > 7 already, however in this specific case, updating from iojs-2.5.0 is breaking a lot of stuff and I just don't have enough time at the moment to inspect it further :'(
Thanks for the heads up though and keep up the awesome work! 👍
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What kind of issue are you submitting?
Bug Report
jshint-loader version 0.8.4
#37 updated
loader-utils
to^1.0.2
. However, fromv0.2.17
(webpack/loader-utils@4130dff)loader-utils
started using ES6 features fromnode >= 4.0.0
.I believe this is a breaking change for everyone using Node < 4 (including
iojs
).The text was updated successfully, but these errors were encountered: