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

@hpe/project-scripts

v1.1.2

Published

HPE JS project scripts

Downloads

125

Readme

HPE JS Project Scripts

Commonly used scripts and utilities to bootstrap your project. This package currently supports eslint and prettier. Jest, react-testing-library and husky support is on the immediate roadmap.

To setup eslint

Before installing dependencies check your project's package.json for existing eslint dependencies, remove any dependencies or dev-dependencies containing eslint as well as any existing .eslintrc files.

  1. In your projects root folder run npm install -D @hpe/project-scripts or yarn add -D @hpe/project-scripts
  2. create a .eslintrc.js in your project's root folder
  3. Add the following snippet to your eslintrc file
const scripts = require('@hpe/project-scripts');
module.exports = scripts.eslint;

Note: If you're running create react app you may see an error when airbnb config tries to load. As humans have not totally mastered package management, the following solution will fix it - rm -rf node_modules && rm yarn.lock && yarn 🙃

  1. Create a .eslintignore file. This file will vary depending on your project structure, here is a good starting point
node_modules/
coverage/
dist/
build/
prod/
out/
.next/
.cache/
public/
yarn.lock
package-lock.json

To setup prettier

Prettier requires some setup on your IDE's end. The following instructions are for VS Code users. Similarly to our eslint setup, you'll need to remove any Prettier dependencies in your project's package.json prior to installing this to avoid dependency conflicts.

  1. Install the Prettier extension from the marketplace.

  2. In your VS Code settings (Preferences -> Settings) click the curly brackets icon in the top right to enable the plain text settings view and add the following:

// Set the default
"editor.formatOnSave": false,
"editor.defaultFormatter": "esbenp.prettier-vscode",
// Enable per-language
"[javascript]": {
    "editor.formatOnSave": true
}
  1. Create a .prettierrc.js in your project's root folder.

  2. Add the following to your prettierrc:

const scripts = require('@hpe/project-scripts');
module.exports = scripts.prettier;
  1. Create a .prettierignore in your root folder.

  2. Similarly to your eslint's ignore file, the contents of this file will depend on your project's structure. Here's a good starting point:

package-lock.json
yarn.lock
.cache
public/
node_modules/
build/
dist/