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

blogfoster-scripts

v0.3.2

Published

> Single-command, zero-config tooling for Node.js projects

Downloads

7

Readme

blogfoster-scripts

Single-command, zero-config tooling for Node.js projects

blogfoster-scripts is a wrapper around some of our favorite JavaScript tools. It unifies developer experience across multiple Node.js projects by hiding other tools and their configs. A CLI with subcommands like lint, format, and build lets us manage tooling for multiple projects much easier. Also, developers don't need to waste time by copy-pasting boilerplate code around just to get tooling working. For more details, check out this blog post.

Installation

We recommend installing blogfoster-scripts locally in your Node.js project with npm i --save-dev blogfoster-scripts.

After that, you can use it with npx or by defining scripts in your package.json:

{
  "scripts": {
    "lint": "blogfoster-scripts lint",
    "format": "blogfoster-scripts format",
    "build": "blogfoster-scripts build"
  }
}

Editor integration

To have editor integrations work for ESLint or Prettier you can create .js config files at the root level of your project that export the configs of this module:

// .eslintrc.js
module.exports = require('blogfoster-scripts/eslint');
// prettier.config.js
module.exports = require('blogfoster-scripts/prettier');

Commands

lint

blogfoster-scripts lint <target>

Check your code for linting issues with ESLint and fix all (fixable) issues.

--check

blogfoster-scripts lint --check <target>

By default, blogfoster-scripts lint will try to fix any fixable linting issues. With the --check argument it will only check your code for issues and exit with a non-zero exit code if there are any.

<target>

Optional file or glob pattern that defines the target to lint. Defaults to **/*.js. Files in /node_modules or /build are ignored. If you want to specify more patterns to ignore you can create a .eslintignore file in the root of your project.

format

blogfoster-scripts format <target>

Check your code for formatting issues with Prettier and fix all (fixable) issues.

--check

blogfoster-scripts format --check <target>

By default, blogfoster-scripts format will try to fix any fixable formatting issues. With the --check argument it will only check your code for issues and exit with a non-zero exit code if there are any.

<target>

Optional file or glob pattern that defines the target to format. Defaults to **/*.{js,json,md}. The package.json, package-lock.json, and files in /node_modules or /build are ignored. If you want to specify more patterns to ignore you can create a .prettierignore file in the root of your project.

build

blogfoster-scripts build

Compile JavaScript starting off from the /src/index.js file, copy static assets from the /assets folder and package everything into the /build folder with Webpack and Babel.

Related

LICENSE

MIT