This project is read-only.

Announcing JSLint.NET 2.0 Beta

The JSLint.NET internals have been overhauled with some significant improvements in 2.0, and we need your help to test it. Please download JSLint.NET 2.0.0 Beta 4 from the releases page or via NuGet and try it out.

Changes at a glance

  • IE9+ is now a requirement
  • Much smaller download
  • Package is now signed

State of the Beta

By and large the beta has been successful. However, there are some lingering stability issues related to threading and message loops. In some circumstances, the new Chakra based JavaScript context simply fails to initialize. Once these issues have been resolved, this work will move into the master branch.

What's new?

In a nutshell, the V8 JavaScript engine is no longer used to run JSLint. Why? Partly because it prevents JSLint.NET from being signed, but most importantly because the entire V8 and it's prerequisites are a huge dependency.

So the number one change in 2.0 is the size of the JSLint.NET package; taking out V8 has dropped it dramatically. For comparison's sake, here is a table showing the changes:

Version File Size Zipped Size Signed
1.4 8.53 MB 3.54 MB No
2.0 beta 732 KB 236 KB Yes

As you can see, the total distribution size for JSLint.NET has gone from over 8MB to under 0.8MB!

Breaking changes

Obviously if V8 has been removed, another JavaScript engine has been put in its place. That engine is Chakra, which makes IE9+ a new requirement for JSLint.NET. That also means that Windows Server 2003 is no longer supported.

In beta 2, the obsolete OutputOverride property in JSLint.NET for MSBuild has been removed.

Other than that, there are no changes to the API or performance of the tool. It's business as usual!

Last edited Apr 5, 2014 at 1:59 AM by Qube, version 8

Comments

No comments yet.