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

@nacelle/eslint-config-nacelle

v1.0.9

Published

Nacelle Code Formatting with ESLint

Downloads

4

Readme

Nacelle Code Formatting with ESLint

What it does

  • Lints JavaScript based on modern standards
  • Fixes formatting issues

This helps us keep all Nacelle Projects formatted consistently.

Installing

While it's possible to use these tools globally, it's best to install on a per-project basis, as follows:

  1. For new projects that don't already have a package.json file, create one with npm init.

  2. Install everything needed by the config:

npx install-peerdeps --dev @nacelle/eslint-config-nacelle
  1. There should now be a big list of devDependencies in package.json

  2. Specify that your project uses this ESLint configuration by doing one of the following:

  • Add the following section to package.json:
"eslintConfig": {
  "extends": [
    "@nacelle/nacelle"
  ],
}

TIP: By adding this snippet into your VSCode snippets file, you can add this to your package.json by just starting to type fmtncl and pressing TAB, as follows:

Video showing VSCode snippet in action - if you can't see this on npmjs.org, try visiting the GitHub repository

  • Alternatively, you could create a .eslintrc file in the project's root directory, containing:
{
  "extends": ["@nacelle/nacelle"]
}

With VS Code

It's a good idea to have VSCode lint and fix for you, instead of having to run eslint . or eslint . --fix. Here's how to set that up:

  1. Install the ESLint package
  2. Now we need to setup some VS Code settings via Code/FilePreferencesSettings. It's easier to enter these settings while editing the settings.json file, so click the {} icon in the top right corner:
"editor.formatOnSave": true,
// turn it off for JS, we will do this via eslint
"[javascript]": {
  "editor.formatOnSave": false
},
// tell the ESLint plugin to run on save
"eslint.autoFixOnSave": true,
// Optional BUT IMPORTANT: If you have the prettier extension enabled for other languages like CSS and HTML, turn it off for JS since we are doing it through Eslint already
"prettier.disableLanguages": ["javascript"],

Credits

This workflow borrows heavily from the No-Sweat™ Eslint and Prettier Setup created by Wes Bos.