jshint4r 0.1.2.1 → 0.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/{README.md → README.rdoc} +5 -24
- data/VERSION +1 -1
- data/jshint4r.gemspec +7 -6
- data/lib/jshint4r/linter.rb +1 -1
- data/lib/jshint4r.rb +0 -2
- data/vendor/jshint/Makefile +23 -0
- data/vendor/jshint/README.md +104 -0
- data/vendor/jshint/jshint.js +2127 -1321
- metadata +8 -7
- data/vendor/jshint/README.markdown +0 -70
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: jshint4r
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.3
|
|
5
5
|
prerelease:
|
|
6
6
|
platform: ruby
|
|
7
7
|
authors:
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2013-
|
|
12
|
+
date: 2013-01-24 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: execjs
|
|
@@ -130,7 +130,7 @@ executables:
|
|
|
130
130
|
extensions: []
|
|
131
131
|
extra_rdoc_files:
|
|
132
132
|
- LICENSE.txt
|
|
133
|
-
- README.
|
|
133
|
+
- README.rdoc
|
|
134
134
|
files:
|
|
135
135
|
- .document
|
|
136
136
|
- .gitmodules
|
|
@@ -138,7 +138,7 @@ files:
|
|
|
138
138
|
- .travis.yml
|
|
139
139
|
- Gemfile
|
|
140
140
|
- LICENSE.txt
|
|
141
|
-
- README.
|
|
141
|
+
- README.rdoc
|
|
142
142
|
- Rakefile
|
|
143
143
|
- VERSION
|
|
144
144
|
- bin/jshint4r
|
|
@@ -170,7 +170,8 @@ files:
|
|
|
170
170
|
- spec/spec_helper.rb
|
|
171
171
|
- spec/support/sample_error.rb
|
|
172
172
|
- vendor/jshint/CHANGELOG
|
|
173
|
-
- vendor/jshint/
|
|
173
|
+
- vendor/jshint/Makefile
|
|
174
|
+
- vendor/jshint/README.md
|
|
174
175
|
- vendor/jshint/jshint.js
|
|
175
176
|
homepage: http://github.com/wtnabe/jshint4r
|
|
176
177
|
licenses:
|
|
@@ -187,7 +188,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
|
187
188
|
version: '0'
|
|
188
189
|
segments:
|
|
189
190
|
- 0
|
|
190
|
-
hash: -
|
|
191
|
+
hash: -509774993189354308
|
|
191
192
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
|
192
193
|
none: false
|
|
193
194
|
requirements:
|
|
@@ -196,7 +197,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
196
197
|
version: '0'
|
|
197
198
|
requirements: []
|
|
198
199
|
rubyforge_project:
|
|
199
|
-
rubygems_version: 1.8.
|
|
200
|
+
rubygems_version: 1.8.23
|
|
200
201
|
signing_key:
|
|
201
202
|
specification_version: 3
|
|
202
203
|
summary: jshint4r
|
|
@@ -1,70 +0,0 @@
|
|
|
1
|
-
JSHint, The (Gentler) JavaScript Code Quality Tool
|
|
2
|
-
==================================================
|
|
3
|
-
|
|
4
|
-
JSHint is a fork of Douglas Crockford's [JSLint](http://jslint.com/) that does
|
|
5
|
-
not tyrannize your code. It is designed to detect errors that actually break your
|
|
6
|
-
code while skipping things that, according to Crockford, “are known to
|
|
7
|
-
contribute mistakes in projects”. In other words, JSHint is a fork of JSLint
|
|
8
|
-
for the real world.
|
|
9
|
-
|
|
10
|
-
For example, JSLint does not tolerate the following constructions:
|
|
11
|
-
|
|
12
|
-
if (cond) statement();
|
|
13
|
-
|
|
14
|
-
It expects all blocks to be enclosed in braces ({}):
|
|
15
|
-
|
|
16
|
-
if (cond) {
|
|
17
|
-
statement();
|
|
18
|
-
}
|
|
19
|
-
|
|
20
|
-
JSHint removes that requirement (but it is still available as an option).
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
Community
|
|
24
|
-
---------
|
|
25
|
-
|
|
26
|
-
The most important part is that JSHint is developed and supported by
|
|
27
|
-
the JavaScript developers community and not by one very opinionated person.
|
|
28
|
-
|
|
29
|
-
If you use JSLint and think that it is too strict, use
|
|
30
|
-
[Issues](https://github.com/jshint/jshint/issues) to describe most annoying
|
|
31
|
-
JSLint gripes you encounter.
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
Development
|
|
35
|
-
-----------
|
|
36
|
-
|
|
37
|
-
JSHint was forked from the JSLint, edition 2010-12-16.
|
|
38
|
-
The current stable edition is [2011-02-19](http://jshint.com/jshint.js).
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
Environments
|
|
42
|
-
------------
|
|
43
|
-
|
|
44
|
-
JSHint can be used as a Node module out of the box:
|
|
45
|
-
|
|
46
|
-
var JSHINT = require("jshint.js").JSHINT;
|
|
47
|
-
|
|
48
|
-
If you use Rhino, we have a special wrapper script for that:
|
|
49
|
-
|
|
50
|
-
java -jar /path/to/js.jar env/rhino.js myscript.js
|
|
51
|
-
|
|
52
|
-
Also included is a Windows Scripting Host wrapper:
|
|
53
|
-
|
|
54
|
-
cscript env/wsh.js myscript.js
|
|
55
|
-
|
|
56
|
-
And if you're on OS X, use Apple's built-in JavaScriptCore:
|
|
57
|
-
|
|
58
|
-
env/jsc.sh myscript.js
|
|
59
|
-
|
|
60
|
-
Tests
|
|
61
|
-
-----
|
|
62
|
-
|
|
63
|
-
To run tests you will need to install [node.js](http://nodejs.org/) and
|
|
64
|
-
expresso. You can install the latter with npm:
|
|
65
|
-
|
|
66
|
-
npm install expresso
|
|
67
|
-
|
|
68
|
-
After that, running tests is as easy as:
|
|
69
|
-
|
|
70
|
-
expresso tests/*.js
|