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

sublime-fixmyjs

v0.3.4

Published

> Sublime plugin to correct JS linting issues

Downloads

2

Readme

sublime-fixmyjs

Sublime plugin to correct JS linting issues

You shouldn't have to care about linting issues. Now you don't have to using fixmyjs.

Preview

Install

Package Control

Install FixMyJS with Package Control and restart Sublime.

You need to have Node.js installed.
Make sure it's in your $PATH by running node -v in your command-line.

Note: On OS X it's expected that Node resides in the /usr/local/bin/ folder, which it does when installed with the default installer. If this is not the case, symlink your Node binary to this location:
ln -s /full/path/to/your/node /usr/local/bin/node

Install from GitHub

  1. Open the Command Palette (Cmd+Shift+P)

  2. Select Package Control > Add Repository

  1. Paste in https://github.com/addyosmani/sublime-fixmyjs

  1. BOOM.

Getting started

In a js file, open the Command Palette (Cmd+Shift+P) and choose FixMyJS. You can alternatively create one or more selections before running the command to only fix those parts.

Options

(Preferences > Package Settings > FixMyJS > Settings - User)

Default

{
		"legacy": true,
		"fixOnSave": false
}

Legacy mode

By default, this plugin uses the FixMyJS legacy mode. This option uses the last stable version of the module which uses JSHint to detect errors in your code and fix them.

It does not include all of the fixes the current version of FixMyJS exposes, but does do a much better job of preserving source formatting. To disable legacy mode, set legacy to false in your user settings for the package.

{
		"legacy": false
}

Keyboard shortcut

You can also set up a keyboard shortcut to run the command by opening up "Preferences > Key Bindings - User" and adding your shortcut with the fix command.

Example:

[
	{ "keys": ["alt+super+j"], "command": "fix" }
]

Project settings

You can override the default and user settings for individual projects. Just add an "FixMyJS" object to the "settings" object in the project's .sublime-project file containing your project specific settings.

Example:

{
	"settings": {
		"FixMyJS": {

		}
	}
}

Kudos

This plugin is based on the excellent Autoprefixer plugin by Sindre Sorhus.

License

MIT © Addy Osmani