npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

bbjshint

v1.0.1

Published

Run JSLint on BBEdit's frontmost text document.

Downloads

12

Readme

bbjshint

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.

install

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`

config

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.

contributors

acknowledgements

See bbresults.

license

MIT