Releases · benquarmby/jslintnet

07 Aug 05:15

v2.3.0

a4612a0

v2.3.0 Latest

Latest

As of edition 2016-06-09, JSLint warns against the use of single quotes to enclose string literals. Check the Google+ community to follow the discussion.

The following code will now produce a warning:

var value = 'a string literal';

And should ideally be written as:

var value = "a string literal";

To tolerate single quote strings, make use of the new single option (issue #27) which is supported in JSLint.NET 2.3.0:

{
  "version": "2.3.0",
  "options": {
    "single": true
  }
}

Issues:

#27 Support "single" option.

Downloads:

JSLint.NET for MSBuild from NuGet
JSLint.NET for Visual Studio from Visual Studio Gallery

Assets 4

22 Apr 23:22

benquarmby

v2.2.2

d109205

v2.2.2

Updated JSLint to edition 2016-04-08.

Handles Date.UTC edge case. See #26.

Downloads:

JSLint.NET for MSBuild from NuGet
JSLint.NET for Visual Studio from Visual Studio Gallery

Assets 4

05 Mar 00:01

benquarmby

v2.2.1

8090723

v2.2.1

Updated JSLint to edition 2016-03-08.

Restores toleration of leading semicolon.

Downloads:

JSLint.NET for MSBuild from NuGet
JSLint.NET for Visual Studio from Visual Studio Gallery

Assets 4

31 Jan 03:56

benquarmby

v2.2.0

2d3e033

v2.2.0

As of edition 2016-01-16, JSLint warns against declaring multiple variables in a single var, let, or const statement. Check the Google+ community to see the original announcement and get involved in the discussion.

The following code will now produce a warning:

var first = true,
    second = false;

And should ideally be written as:

var first = true;
var second = false;

While this may seem like a striking about-face from the "old" version, JSLint has allowed either form ever since the ES6 rewrite back in May of 2015. With the advent of let and const (and a smarter JSLint), grouping all variables within a single statement is neither necessary nor recommended.

To tolerate combined var, let or const statements, make use of the new multivar option (issue #20) which is now fully supported in JSLint.NET 2.2.0:

{
  "version": "2.2.0",
  "options": {
    "multivar": true
  }
}

Issues:

#20 Support multivar option.

Downloads:

JSLint.NET for MSBuild from NuGet
JSLint.NET for Visual Studio from Visual Studio Gallery

Assets 4

17 Jan 05:39

benquarmby

v2.1.0

6b3778a

v2.1.0

Version 2.1.0 adds first class support for the property directive that JSLint can generate. In particular, JSLint.NET for Visual Studio has a new "Generate Property Directive" context menu item within the code editor.

As the name implies, this will inject (or replace) a directive based on all the property names in the current JavaScript file.

/*property
    getElementsByTagName, getTime, hasOwnProperty, id, indexOf, inited,
    removeChild, replace, require, requireModules, requireType, shift, shim,
    unnormalized, uri, url, usingExports, waitSeconds
*/

This should be particularly helpful with Angular app development, since it relies on property names with dangling special characters (see #12 and #16). Property names within this directive are considered deliberate and exempt from quality checks.

Issues: