All library files have their original headers preserved, and so license and ownership information for them can be found there. All files belonging to this project are licensed thusly:
Copyright 2011 Jason Duncan, Nicholas Ortenzio
This file is part of the JSLint Extension for Google Chrome.
The JSLint Extension for Google Chrome is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
The JSLint Extension for Google Chrome is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with the JSLint Extension for Google Chrome. If not, see http://www.gnu.org/licenses/.
This extension adds the ability to run any scripts loaded into the current page through Douglas Crockford’s JSLint implementation.
There are no external dependencies for the extension itself, but building it requires ruby and rake.
The rake build task will copy all the necessary files into a directory
called output/.
After building, the extension can be installed as follows (as of Chrome version 10.0.612.1 dev):
- From Chrome, click the tool menu button.
- Click Tools -> Extensions.
- Click the plus sign “+” next to “Developer Mode”. This step is not necessary if Developer Mode is already open.
- Click the “Load Unpacked Extension” button.
- Navigate to the
output/directory under the project checkout directory and click the “Open” button.
Installing the extension as described above will add a button next to the url bar in Chrome. Clicking that button will show a small popup with a drop down list of all the javascript files loaded in the current page. Choose the file to be examined in the list, and click the “JSLint” button. Results will be shown in the popup.
The output/ directory is only for the built version of the extension. When
editing files in the project, you’ll want to edit them in their respective
source locations. All javascripts go in src/, all static content (images,
html files, css files, the manifest, etc.) belongs in content/. When you’re
ready to do a live test of your changes, simply rebuild and then reload the
extension in Chrome using the steps outlined above.
All scripts in the project are covered 100% by unit tests, because the code was
written test first. To run the tests, simply point Chrome to the url
file:///path/to/project/location/jslint_chrome/test/unit/tests.html