JavaScript Source Code Analyzer [closed]

Question

Closed. This question is seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. It does not meet Stack Overflow guidelines. It is not currently accepting answers.

We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.

Closed 9 years ago.

Improve this question

Does anyone know of a good, extensible source code analyzer that examines JavaScript files?

Pretty much, the typical errors and compatibility issue analysis but also the ability to examine naming conventions and style as well. — JamesEggers
– JamesEggers, Commented Dec 1, 2008 at 16:36
Can you provide an example code analyzer for a different language? — Chris MacDonald
– Chris MacDonald, Commented Dec 1, 2008 at 16:39
An example of what I would like to see is something like MS's StyleCop or FXCop but for JavaScript instead of C# or MSIL bytecode. — JamesEggers
– JamesEggers, Commented Dec 1, 2008 at 16:46
After years of using both JSHint and JSLint, I moved the answer to JSHint. JSLint, in my opinion, is too opinionated and strict. — JamesEggers
– JamesEggers, Commented Apr 13, 2012 at 12:54

CodeNaked · Accepted Answer · 2011-06-15 14:08:28Z

61

In the interest of keeping this question up-to-date, there is a fork of JSLint called JSHint. An explanation of why JSHint was created can be found here, but to summarize:

JSHint is a fork of JSLint, the tool written and maintained by Douglas Crockford. JSLint served me well for quite some time but in the past few months it has gotten uncomfortably opinionated and hostile towards your code. It is quickly transforming from a tool that helps developers to prevent bugs to a tool that makes sure you write your code like Douglas Crockford.

answered Jun 15, 2011 at 14:08

CodeNaked

41.6k6 gold badges128 silver badges151 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

CodeNaked Over a year ago

Ha, a down vote :-) Was that you Douglas?

JamesEggers Over a year ago

While this is an older question by now, I moved the answer to JSHint. I respect both JSLint and JSHint; however, JSLint is way too opinionated and strict for me. JSHint allows the style freedom that I prefer (namely comma-first) and still provides a lot of power in terms of validation.

chills42 · Accepted Answer · 2014-03-21 15:30:03Z

23

JSLint has historically been the main tool for this, but several more now exist:

JSHint - a fork of JSLint that is said to be a little less opinionated
Closure Linter - a linter that checks against the Google Javascript Style Guide
ESLint - a more flexible tool, but newer, and not yet as stable.

edited Mar 21, 2014 at 15:30

answered Dec 1, 2008 at 16:33

chills42

14.6k4 gold badges45 silver badges78 bronze badges

Comments

Bernhard Hofmann · Accepted Answer · 2011-06-17 22:30:41Z

4

If you haven't found it yet, you should take a look at Google Closure Compiler. Compiles your JavaScript and finds errors in code. http://code.google.com/closure/compiler/docs/gettingstarted_api.html

answered Jun 17, 2011 at 22:30

Bernhard Hofmann

10.4k12 gold badges65 silver badges80 bronze badges

Comments

learner_19 · Accepted Answer · 2013-09-08 15:58:09Z

4

I tried out ESlint and found it good..you can also add custom rules there..Here is the github repo: https://github.com/nzakas/eslint

answered Sep 8, 2013 at 15:58

learner_19

4,1411 gold badge21 silver badges8 bronze badges

Comments

Msonic · Accepted Answer · 2012-04-13 14:43:26Z

2

JSAnalyse has just been published on codeplex. It is a tool which analyses the dependencies between javascript files. You can even define the allowed dependencies and JSAnalysis checks whether the defined rules are fulfilled or not. That allows to keep track about the javascript dependencies even in big projects and to have a clean architecture.

JSAnalyse can be executed as a command line tool or configured via the Visual Studio Layer Diagramm. It is also easy to integrate into the build. With gated check-ins you can keep the dependencies under control.

edited Apr 13, 2012 at 14:43

Msonic

1,45415 silver badges25 bronze badges

answered Apr 13, 2012 at 7:11

Thomas Schmitt

291 bronze badge

1 Comment

JamesEggers Over a year ago

Looks interesting. The only thing that I don't like from a quick look is that it requires .Net (and Visual Studio?). I don't know if someone could use this for analyzing their JS in Python, Ruby, Java, etc. Regardless, it DOES look interesting and will have to check it out. Thanks for adding the answer.

gusridd · Accepted Answer · 2013-03-28 01:33:03Z

2

There exist a parser called ECMAScript parsing infrastructure for multipurpose analysis (esprima) located at http://esprima.org/ with several example tools that can be used in some analysis

ECMAScript parsing infrastructure for multipurpose analysis

answered Mar 28, 2013 at 1:33

gusridd

88410 silver badges16 bronze badges

Comments

user_19 · Accepted Answer · 2013-09-08 16:42:46Z

2

Apart from JSLint, JSHint, ESLint, Plato, Google Closure-Linter there's another tool named Esprima. Here is the link for it: http://esprima.org/

Also, this is the github link for the tool Esprima: https://github.com/ariya/esprima

I faced installation issues while trying out Google Closure-Linter for Windows. But, it does mention on the web page that its support for Windows is experimental. All other tools are easy to use.

answered Sep 8, 2013 at 16:42

user_19

5991 gold badge8 silver badges13 bronze badges

Comments

JamesEggers · Accepted Answer · 2008-12-01 16:33:56Z

1

I have found JSLint which helps correct a lot of common errors and such; however, I'm hoping to find something that I can add my own rules and such to help automate some coding standards stuff that my company is wanting to implement into JavaScript.

http://www.jslint.com/

I need to look into it's extensibility model more.

answered Dec 1, 2008 at 16:33

JamesEggers

13k14 gold badges66 silver badges89 bronze badges

1 Comment

chills42 Over a year ago

I'd love to see something more powerful too, but I haven't found anything yet...

Stein G. Strindhaug · Accepted Answer · 2008-12-01 18:57:29Z

1

There's a few tools on the list of tools for static code analysis at wikipedia that has JavaScript support, you can allso see JavaScript Debugging if any of the tools mentioned would help. There's allso a few good tools at YUI (Yahoo! Developer Network), as well as a lot of helpful components.

I've allways used JSLint myself, and that's the only analysis tool for JS I've tried. I've grown more and more fond of JavaScript, but good tools is still a problem. :(

answered Dec 1, 2008 at 18:57

Stein G. Strindhaug

5,1272 gold badges31 silver badges42 bronze badges

Comments

BozoJoe · Accepted Answer · 2011-01-25 20:07:27Z

1

I use Aptana for JavaScript file analysis. It catches alot of goofs (if condition with a single =). It also describes the class layout. I believe it has a jslint implementation embedded in it.

answered Jan 25, 2011 at 20:07

BozoJoe

6,5344 gold badges48 silver badges70 bronze badges

Collectives™ on Stack Overflow

JavaScript Source Code Analyzer [closed]

10 Answers 10

2 Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

1 Comment

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

10 Answers 10

2 Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

1 Comment

Comments

Comments

Linked

Related