Closed pwcberry closed 9 years ago
That's a great question, and something I've been thinking about since Crockford announced the JSLint rewrite in Feb.
There are a few things that are holding it back right now:
With all of that said, it is definitely going to happen. I'm just not sure when yet.
OK, so Crockford just dropped the beta version and made the source available. Things will start to move a bit faster now. I can see a JSLint.NET 2.0 Beta soon.
Thanks for the update! I think releasing v2 of JSLint.NET for ES6 is the right approach.
I've just posted the 2.0.0-beta5 pre-release that wraps JSLint ES6. Check out the beta page for some extra detail.
Beta 6 has just been posted, and is likely to be the last beta before a final release. I've also created an upgrade announcement wiki page to get everyone ready for the breaking changes.
Douglas Crockford is still fielding some bug reports from the community, but I expect that will settle down soon. So I think JSLint.NET 2.0 will be ready to go in a matter of weeks now.
The ES6 branch has now been merged and released.
IE11 and the evergreen browsers (Firefox and Chrome) now support many features of ES6 such as keywords and types.
Application developers who are not required to support older browsers would like to write safe JavaScript code using these new features.
As Crockford is working on a new version of JSLint, JSLint.NET should be updated to work with ES6.