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

@phoenix-plugin-registry/com.github.mrmeku.closure-linter

v0.4.0

Published

Lint javascript files according to the Google style guide and automatically fix linting errors.

Downloads

66

Readme

brackets-closure-linter

A Brackets extension that provides hooks to the Closure Linter. The Closure Linter is a utility that checks JavaScript files for style issues such as operator placement, missing semicolons, spacing, the presence of JsDoc annotations, and more.

Installation

To install, place in your brackets/src/extensions/user folder. Alternatively,open the extension manager within brackets and install the Closure Linter package.

Brackets has JSLint built in and if you wish to ignore JSLint results, you must tell Brackets to explicitly use gjslint only. This can be done via a .brackets.json file in the root of your project or going clicking Debug > Open Preferneces File to edit your global preferences. Simply use this block:

"language": {
    "javascript": {
        "linting.prefer": "gjslint",
        "linting.usePreferredOnly": true
    }
}

Requirements

python must be set within your path since the closure linter is a python executable

Usage

After installation, the closure linter's gjslint` becomes your default javascript linter. To see it in action, open a JavaScript file. In the bottom right corner of your editor you will either see a green checkmark (which means no problems were found) or a yellow exclamation mark. Click on the exclamation mark and a bottom panel will open listing all the problems found.

The closure linter also comes bundled with a fixjsstyle command which can automatically fix identified linting errors. To see it in action, open a JavaScript file. If you see a yellow exclamation mark in the bottom right corner of your editor, you have linting errors that fixjsstyle may be able to fix. Select Edit > Fixjsstyle menu or Cmd-Shift-J(Mac) / Ctrl-Shift-J(Win) to run the command. Then save your file and watch your linting errors disappear!

You can also have fixjsstyle run automatically whenever you save a javascript or html document by selecting Edit > Fixjsstyle On Save.

Files

  • main.js:
    • Sets up menu items for fixjsstyle and fixjsstyle on save
    • When brackets is ready, gjslint is registered to lint both a javascript html
  • closureLinterDomain.js:
    • A node instance which creates a temporary file copied from the editor's current text and runs the closure linter
  • closure_linter/:
    • Google's closure linter