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

@aptuitiv/eslint-config-aptuitiv

v1.0.0

Published

eslint configuration for websites built by Aptuitiv

Downloads

34

Readme

eslint Configuration

The purpose of this repository is to centralize the eslint configuration for Aptuitiv website projects. It's intended that this would be included into each project. By having this in one spot we can update eslint rules for all of our projects and keep things centralized.

Installing

Install this library and eslint-plugin-import with NPM.

npm i -D @aptuitiv/eslint-config-aptuitiv eslint-plugin-import

Usage

Create a .eslintrc.js file in the root of your project. Because the eslint configuration will be in this plugin, we only need some minimal code in the eslintrc.js file.

module.exports = {
    extends: ['@aptuitiv/eslint-config-aptuitiv']
}

That will essentially tell eslint to use this package for the eslint configuration.

Development

When developing this plugin it's best to work on it locally and test it in a project locally.

  • First, navigate in the command line to the folder for this package on your computer. Run npm link.
  • Then, navigate to the folder for the project you want to use this in and run npm link @aptuitiv/eslint-config-aptuitiv

If you're just changing the rules then you don't need to run npm link again. But if you install any new packages then you'll need to run the npm link command as described above for both this plugin and the project you're testing it with.

When you're done testing you need to remove the symlinks. Do the following.

  1. In the project root folder run npm unlink --no-save @aptuitiv/eslint-config-aptuitiv.
  2. In the root folder for this library run npm unlink.

You must do it in that order. See NPM Linking and Unlinking for more information if you have issues.

NPM link resources:

Publishing to NPM is done like this:

  1. Update the version with npm version minor, npm version patch, or npm version major depending on the type of update.
  2. Publish with npm publish

Pull requests are welcome!