JSLint for Visual Studio 2010

Created Issue: Skip on build option missing in VS 2010 context menu [1557]

dmitrykiev — Tue, 14 May 2013 16:24:24 GMT

![Image](http://i.imgur.com/iVHR05L.png)

Commented Issue: JSLint Stops on For Loop [1549]

Qube — Wed, 08 May 2013 00:44:56 GMT

Every time JSLint comes across a For loop in my code, it stops prematurely.

```
for (var i = 0; i < attributes.length; i++) {
```

> Warning 2 JS Lint: Stopping. (24% scanned).
Comments: ** Comment from web user: Qube **

JSLint for Visual Studio runs jslint.js without any alterations. If it's not behaving as you expect, I recommend raising it with the author of JSLint:
https://plus.google.com/communities/104441363299760713736

I believe this is a known issue though, and there is probably already a discussion for it on the old Yahoo group:
http://tech.groups.yahoo.com/group/jslint_com/

Commented Issue: JSLint Stops on For Loop [1549]

Nitron_F117 — Tue, 30 Apr 2013 12:52:20 GMT

That does work, but the var declaration inside the for loop is valid and should not break the tool.

Commented Issue: JSLint Stops on For Loop [1549]

dgersten — Tue, 30 Apr 2013 12:17:46 GMT

try moving your var declaration outside.

Created Issue: JSLint Stops on For Loop [1549]

ldevlin — Mon, 29 Apr 2013 19:41:43 GMT

Every time JSLint comes across a For loop in my code, it stops prematurely.

```
for (var i = 0; i < attributes.length; i++) {
```

> Warning 2 JS Lint: Stopping. (24% scanned).

Updated Release: 1.4.2 (Oct 06, 2012)

Qube — Sat, 30 Mar 2013 11:33:38 GMT

1.4.2

Released: 1.4.2 (out 06, 2012)

Sat, 30 Mar 2013 11:33:38 GMT

1.4.2

Source code checked in, #25345

Qube — Sat, 30 Mar 2013 11:28:47 GMT

Fixed broken tests. Added missing documentation.

Source code checked in, #25212

Qube — Tue, 26 Mar 2013 05:50:32 GMT

Assume a text report file unless it has an html extension.

Commented Issue: Excluding JS file that are included in the project via Content Include? [1477]

jtheriault — Wed, 20 Mar 2013 21:09:23 GMT

We have multiple products that all use some common folders. We're using Visual Studio's ability to include content in a project from outside the project (Content Include) for third party JS libraries and code we write for all projects to use. The code from the third party libraries often don't conform to jsLint or jsHint requirements, so when we run jsHint on our project at build, it reports tons of errors.

We've tried to exclude these folders from jsLint for VS2012 using the provided mechanisms (right click, exclude on build), but whenever the build runs, the files are still checked and errors are reported.

Can anyone tell me the correct way to have these files excluded from these project's build process?

For example, if I have the following Content Include key in .proj file, what is the correct jsLintSkip entry to have in the .proj file to avoid running jsLint on this file?

Given:
__<Content Include="vendor\jQuery\jquery.min.js" />__

What is the correct value for <jsLintSkip> to exclude this included vendor folder so that this file (jQuery) and other's like are _NOT_ run through jsLint at build?

__<JSLintSkip>vendor\</JSLintSkip> (?)__
Comments: ** Comment from web user: jtheriault **

It looks as if IsNodeSkipped wrongly assumes a relative name for project items.

New Post: Excluding JS file that are included in the project via Content Include?

kpepin — Wed, 20 Mar 2013 19:22:09 GMT

We have multiple products that all use some common folders. We're using Visual Studio's ability to include content in a project from outside the project (Content Include) for third party JS libraries and code we write for all projects to use. The code from the third party libraries often don't conform to jsLint or jsHint requirements, so when we run jsHint on our project at build, it reports tons of errors.

We've tried to exclude these folders from jsLint for VS2012 using the provided mechanisms (right click, exclude on build), but whenever the build runs, the files are still checked and errors are reported.

Can anyone tell me the correct way to have these files excluded from these project's build process?

For example, if I have the following Content Include key in .proj file, what is the correct jsLintSkip entry to have in the .proj file to avoid running jsLint on this file?

Given:
<Content Include="vendor\jQuery\jquery.min.js" />

What is the correct value for <jsLintSkip> to exclude this included vendor folder so that this file (jQuery) and other's like are run through jsLint at build?

<JSLintSkip>vendor\</JSLintSkip> (?)

Created Issue: Excluding JS file that are included in the project via Content Include? [1477]

kpepin — Tue, 19 Mar 2013 14:41:20 GMT

We have multiple products that all use some common folders. We're using Visual Studio's ability to include content in a project from outside the project (Content Include) for third party JS libraries and code we write for all projects to use. The code from the third party libraries often don't conform to jsLint or jsHint requirements, so when we run jsHint on our project at build, it reports tons of errors.

We've tried to exclude these folders from jsLint for VS2012 using the provided mechanisms (right click, exclude on build), but whenever the build runs, the files are still checked and errors are reported.

Can anyone tell me the correct way to have these files excluded from these project's build process?

For example, if I have the following Content Include key in .proj file, what is the correct jsLintSkip entry to have in the .proj file to avoid running jsLint on this file?

Given:
__<Content Include="vendor\jQuery\jquery.min.js" />__

What is the correct value for <jsLintSkip> to exclude this included vendor folder so that this file (jQuery) and other's like are run through jsLint at build?

<JSLintSkip>vendor\</JSLintSkip> (?)

Created Issue: Support Configuration via .jshintrc [1461]

wrumsby — Sun, 10 Mar 2013 21:32:53 GMT

JSHint configuration can be stored in a `.jshintrc` JSON file.

It should be possible to for the extension to:

* look for a `.jshintrc` file in the current project or solution and use that
* export settings as a `.jshintrc` file
* import settings from a `.jshintrc` file

I also think the extension should save settings to a `.jshintrc` file so that other tools that support JSHint (e.g. Grunt) can use the same settings.

More details about JSHint configuration are [here](http://www.jshint.com/docs/).

Source code checked in, #24481

Qube — Sun, 10 Mar 2013 04:22:50 GMT

Added text and HTML reporting options to MSBuild task.

Patch Uploaded: #14010

rufwork — Wed, 06 Mar 2013 15:06:58 GMT

rufwork has uploaded a patch.

Description:
Mr. Crockford has updated JSLint a number of times since December 3rd, 2012, and, selfishly (as we're all but mandating use of this plug-in company-wide), I'd like to see the change to JSLint.js from last Jan 29th incorporated.

I am uploading the most recent copy of JSLint.js, dated 2013-02-18, commit 6a79e7cc8b751698d3e052b5b3dc44659d9ce9b9 : https://github.com/douglascrockford/JSLint/commit/6a79e7cc8b751698d3e052b5b3dc44659d9ce9b9#jslint.js

The issue we discovered in JSLint is described here:
http://tech.groups.yahoo.com/group/jslint_com/message/3109

JSLint disliked:
if (typeof foo === 'undefined') {

JSLint liked:
if (foo === undefined) {

But JSLint (so also JSLint.VS2010) would accept:
if ('undefined' === typeof foo) {

We actually have a fair amount of code written that took advantage of that loophole that I'd like to have the extension help me weed and keep out.

I'm successfully using the latest version of JSLint in a custom TFS check-in policy that is largely based on JSLint.VS2010, so this shouldn't cause pain.

Thanks.

New Post: JSHint swindent(?)

kpepin — Tue, 05 Mar 2013 19:37:32 GMT

Is there support for the JSHint option for switch case indenting ("swindent")?

https://github.com/jshint/jshint/pull/600

switch (me.options.type()) {
    case me.Types.radio:
        result = me.Types.radio;
        break;
    case me.Types.checkbox:
        result = me.Types.checkbox;
        break;
    case me.Types.button:
        result = me.Types.button;
        break;
}

Created Issue: Support for the JSHint swindent key? [1446]

kpepin — Tue, 05 Mar 2013 19:35:55 GMT

In the following URL, the JSHint team added support for the switch indent option, and I was hoping we could get similar support for this feature in the jsLint for Visual Studio extension? Havign case statements indented from their parent switch is a whole lot easier to read.

https://github.com/jshint/jshint/pull/600

Thanks,
Keith

An example of a switch case that currently gets indent errors:
```
switch (me.options.type()) {
case me.Types.radio:
result = me.Types.radio;
break;
case me.Types.checkbox:
result = me.Types.checkbox;
break;
case me.Types.button:
result = me.Types.button;
break;
}
```

Source code checked in, #24305

Qube — Mon, 04 Mar 2013 08:55:19 GMT

Added version and copyright to MSBuild assembly info. Fixed mismatched build configuration for release.

Source code checked in, #24279

Qube — Sat, 02 Mar 2013 13:29:51 GMT

Switched from using source directory to source files in MSBuild task. Added integration tests with example projects.

Commented Feature: Create a command line interface to jslint [616]

Qube — Thu, 28 Feb 2013 23:41:26 GMT

from barsuk:

Hello,

I'd like to use the same tool on the developer computer and in my central TFS builds. How can I use it? The preferred way were not to start Visual Studio during the builds on the TFS Build Server.

Kind regards,

Alexander

from lukepage:

I'd like to add this feature.

My plan is to

1. Create an executable version of the extension

2. Be able to define "configurations" that the extension and binary can use
Comments: ** Comment from web user: Qube **

I've just checked in an MSBuild task project. I'm hoping it'll improve the CI + JSLint story for Microsoft environments (TFS specifically). Maybe it will solve the problem for you if you haven't already rolled your own.