blocks|key|3295061|text|为了使这个问题保持最新，有一个名为JSHint的JSLint分支。可以在here中找到创建JSHint的原因的解释，但总结如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3295062|3295063|+JSHint是由Douglas+Crockford编写和维护的工具JSLint的分支。JSLint在相当长的一段时间内为我提供了很好的服务，但在过去的几个月里，它变得令人不快地固执己见，并对您的代码充满敌意。它正在迅速地从一个帮助开发人员防止bug的工具转变为一个确保您编写代码的工具，就像Douglas+Crockford。|blockquote|3295064|3295065|entityMap|0|LINK|mutability|MUTABLE|url|http://jshint.com/|1|http://anton.kovalyov.net/2011/02/20/why-i-forked-jslint-to-jshint/^0|H|6|0|10|4|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|10|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|11|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

In the interest of keeping this question up-to-date, there is a fork of JSLint called <a href="http://jshint.com/">JSHint</a>. An explanation of why JSHint was created can be found <a href="http://anton.kovalyov.net/2011/02/20/why-i-forked-jslint-to-jshint/">here</a>, but to summarize:

<blockquote>
 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.
</blockquote>

blocks|key|4139944|text|JSLint在历史上一直是主要的工具，但现在还存在更多的工具：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4139945|4139946|JSHint+-一个据说比Google+Javascript+Style+Guide|unordered-list-item|4139947|ESLint小一点的JSLint分支-一个检查Google+Javascript+Style+Guide|4139948|ESLint的JSLint-一个更灵活的工具，但更新，还不稳定。|4139949|4139950|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jslint.com/|1|http://jshint.com/|2|http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml|3|https://github.com/eslint/eslint|4|5^0|0|6|0|0|0|0|6|1|D|T|2|0|0|6|3|N|T|4|0|0|6|5|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|-4|5|6|7|16|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|17|8|@]|9|@$A|18|B|19|1|1A]|$A|1B|B|1C|1|1D]]|C|$]]|$1|H|3|I|5|G|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]|$A|1I|B|1J|1|1K]]|C|$]]|$1|J|3|K|5|G|7|1L|8|@]|9|@$A|1M|B|1N|1|1O]]|C|$]]|$1|L|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|X]]|Y|$5|P|Q|R|C|$S|Z]]|10|$5|P|Q|R|C|$S|X]]|11|$5|P|Q|R|C|$S|Z]]]]

<a href="http://www.jslint.com/" rel="noreferrer">JSLint</a> has historically been the main tool for this, but several more now exist:

<ul>
<li><a href="http://jshint.com/" rel="noreferrer">JSHint</a> - a fork of JSLint that is said to be a little less opinionated</li>
<li><a href="https://developers.google.com/closure/utilities/" rel="noreferrer">Closure Linter</a> - a linter that checks against the <a href="http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml" rel="noreferrer">Google Javascript Style Guide</a></li>
<li><a href="https://github.com/eslint/eslint" rel="noreferrer">ESLint</a> - a more flexible tool, but newer, and not yet as stable.</li>
</ul>

blocks|key|3295128|text|如果你还没有找到它，你应该看看Google+Closure+Compiler。编译JavaScript并查找代码中的错误。http://code.google.com/closure/compiler/docs/gettingstarted_api.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3295129|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/closure/compiler/docs/gettingstarted_api.html^0|1P|1W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

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

blocks|key|905415|text|我尝试过ESlint，发现good..you还可以添加自定义规则there..Here是github存储库：https://github.com/nzakas/eslint|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|905416|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nzakas/eslint^0|1I|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I tried out ESlint and found it good..you can also add custom rules there..Here is the github repo: <a href="https://github.com/nzakas/eslint" rel="nofollow">https://github.com/nzakas/eslint</a>

blocks|key|905398|text|JSAnalyse刚刚在Codeplex上发布。这是一个分析javascript文件之间依赖关系的工具。您甚至可以定义允许的依赖关系和JSAnalysis检查所定义的规则是否得到满足。这使得即使在大型项目中也可以跟踪javascript依赖关系，并拥有一个干净的架构。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|905399|JSAnalyse可以作为命令行工具执行，也可以通过Visual+Studio+Layer+Diagramm配置。它也很容易集成到构建中。使用门控签入，您可以控制依赖项。|905400|entityMap|0|LINK|mutability|MUTABLE|url|http://jsanalyse.codeplex.com/^0|1V|A|30|A|0|9|0|0|0|9|Q|S|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

<a href="http://jsanalyse.codeplex.com/" rel="nofollow">JSAnalyse</a> 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 <code>JSAnalysis</code> checks whether the defined rules are fulfilled or not. That allows to keep track about the <code>javascript</code> dependencies even in big projects and to have a clean architecture.

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

blocks|key|3295181|text|在http://esprima.org/上有一个名为用于多用途分析的ECMAScript解析基础结构(esprima)的解析器，其中有几个可用于某些分析的示例工具|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3295182|ECMAScript+parsing+infrastructure+for+multipurpose+analysis+|3295183|entityMap|0|LINK|mutability|MUTABLE|url|http://esprima.org/|1^0|1|J|0|0|0|1O|1|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|F|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|M]]]]

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

<a href="http://esprima.org/" rel="nofollow">ECMAScript parsing infrastructure for multipurpose analysis </a>

blocks|key|73688|text|除了JSLint，JSHint，ESLint，柏拉图，谷歌Closure-Linter还有另一个工具叫做Esprima。这是它的链接：http://esprima.org/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|73689|此外，这是工具Esprima的github链接：https://github.com/ariya/esprima|73690|我在尝试Google+Closure-Linter+for+Windows时遇到了安装问题。但是，它确实在网页上提到，它对Windows的支持是实验性的。所有其他工具都很容易使用。|73691|entityMap|0|LINK|mutability|MUTABLE|url|http://esprima.org/|1|https://github.com/ariya/esprima^0|1V|J|0|0|O|W|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Apart from JSLint, JSHint, ESLint, Plato, Google Closure-Linter there's another tool named Esprima.
Here is the link for it: <a href="http://esprima.org/" rel="nofollow">http://esprima.org/</a>

Also, this is the github link for the tool Esprima: <a href="https://github.com/ariya/esprima" rel="nofollow">https://github.com/ariya/esprima</a>

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.

blocks|key|899920|text|我发现了JSLint，它可以帮助纠正许多常见的错误等等；但是，我希望找到一些我可以添加自己的规则的东西，以帮助将我的公司想要在JavaScript中实现的一些编码标准的东西自动化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|899921|http://www.jslint.com/|offset|length|899922|我需要更多地研究它的可扩展性模型。|899923|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|M|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

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.

<a href="http://www.jslint.com/" rel="nofollow noreferrer">http://www.jslint.com/</a>

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

blocks|key|73370|text|在维基百科的list+of+tools+for+static+code+analysis上有一些支持JavaScript的工具，如果上面提到的工具对你有帮助，你也可以访问JavaScript+Debugging。在YUI上有很多很好的工具。开发人员网络)，以及许多有用的组件。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|73371|我自己一直在使用JSLint，这是我唯一尝试过的JS分析工具。我越来越喜欢JavaScript了，但是好的工具仍然是个问题。:(|73372|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis|1|http://en.wikipedia.org/wiki/JavaScript#Debugging|2|http://developer.yahoo.com/yui/^0|6|12|0|2D|K|1|2Z|3|2|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

There's a few tools on the <a href="http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis" rel="nofollow noreferrer">list of tools for static code analysis</a> at wikipedia that has JavaScript support, you can allso see <a href="http://en.wikipedia.org/wiki/JavaScript#Debugging" rel="nofollow noreferrer">JavaScript Debugging</a> if any of the tools mentioned would help. There's allso a few good tools at <a href="http://developer.yahoo.com/yui/" rel="nofollow noreferrer">YUI</a> (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. :(

blocks|key|3294994|text|我使用Aptana进行JavaScript文件分析。它捕获了很多愚蠢的东西(如果条件中只有一个=)。它还描述了类布局。我相信它有一个嵌入的jslint实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3294995|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

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

JavaScript Source Code Analyzer

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有没有人知道一个好的、可扩展的源代码分析器，可以检查JavaScript文件？

问JavaScript源代码分析器
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JavaScript源代码分析器EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JavaScript源代码分析器
EN