Run JSHint on the javascript code in your frontmost (and saved) BBEdit document, and see the results in a Result Browser window.
Note that for now, the text document must be saved before bbjshint can check it.
Use from BBEdit's Scripts menu by either installing or symlinking bbjshint to BBEdit's Scripts folder. This is ~/Library/Application Support/BBEdit/Scripts or perhaps ~/Dropbox/Application Support/BBEdit/Scripts. You can show this folder from BBEdit by going to the scripts menu and choosing "Open Scripts Folder".
npm install --global bbjshint (or, sudo npm install --global bbjshint)
cd ~/Library/Application\ Support/BBEdit/Scripts/
ln -s `which bbjshint`
bbjshint will use the first .jshintrc file it finds, starting from the directory of the document being checked, and looking in each subsequent parent directory. If no .jshintrc file is found, then ./jshint-flags.json will be used.
Comments are also allowed in the .jshintrc, as seen in this example.
See bbresults.
MIT
FAQs
Run JSLint on BBEdit's frontmost text document.
The npm package bbjshint receives a total of 4 weekly downloads. As such, bbjshint popularity was classified as not popular.
We found that bbjshint demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."