aboutsummaryrefslogtreecommitdiff
path: root/devel/jsl/pkg-descr
diff options
context:
space:
mode:
authorBrian Somers <brian@FreeBSD.org>2008-05-28 18:15:24 +0000
committerBrian Somers <brian@FreeBSD.org>2008-05-28 18:15:24 +0000
commitffca83ab4db8b48d52734f9fa14d7f1c91099c23 (patch)
tree257e736659f619d2f984b2aeb10a2711d9cf4a7f /devel/jsl/pkg-descr
parentba10f33afc325ae9bdd745b697e44318b5408f6d (diff)
Notes
Diffstat (limited to 'devel/jsl/pkg-descr')
-rw-r--r--devel/jsl/pkg-descr20
1 files changed, 20 insertions, 0 deletions
diff --git a/devel/jsl/pkg-descr b/devel/jsl/pkg-descr
new file mode 100644
index 000000000000..ef1121a9261c
--- /dev/null
+++ b/devel/jsl/pkg-descr
@@ -0,0 +1,20 @@
+Many JavaScript implementations do not warn against questionable coding
+practices. Yes, that's nice for the site that "works best with Internet
+Explorer" (designed with templates, scripted with snippets copied from
+forums). But it's a nightmare when you actually want to write quality,
+maintainable code.
+
+That's where JavaScript Lint comes in. With JavaScript Lint, you can
+check all your JavaScript source code for common mistakes without actually
+running the script or opening the web page.
+
+JavaScript Lint holds an advantage over competing lints because it is
+based on the JavaScript engine for the Firefox browser. This provides
+a robust framework that can not only check JavaScript syntax but also
+examine the coding techniques used in the script and warn against
+questionable practices.
+
+WWW: http://www.javascriptlint.com/
+
+- Brian Somers
+brian@FreeBSD.org