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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sleepingasteroid/bluehop-editor-config

v0.1.0

Published

Shared .editorconfig and VSCode settings, applied into a project with one command.

Downloads

325

Readme

@sleepingasteroid/bluehop-editor-config

Drop a shared .editorconfig and VS Code workspace settings into any project with one command, so every editor behaves the same way.

What is this?

Different editors (and different people) use different defaults — tabs vs spaces, line endings, whether code formats on save. That leads to noisy diffs and "works on my machine" formatting fights.

This package fixes that by giving you ready-made editor settings you can copy into any project with one command:

  • An .editorconfig — a standard file most editors read automatically, so basics like indentation and line endings are consistent for everyone.
  • VS Code workspace settings — turns on format-on-save, sets Prettier as the default formatter, and enables ESLint's flat config.
  • VS Code extension recommendations — so collaborators get prompted to install the right extensions.

Why use it?

  • Consistent editor behavior for everyone on the project, automatically.
  • One command instead of copy-pasting dotfiles between repos.
  • Files are copied, not linked, so you can still tweak them per project.

Install

pnpm add -D @sleepingasteroid/bluehop-editor-config

Use

npx bluehop-editor-config          # writes the files, skipping any that already exist
npx bluehop-editor-config --force  # overwrite existing files

This creates:

  • .editorconfig
  • .vscode/settings.json — format on save, ESLint flat config, Prettier as default formatter
  • .vscode/extensions.json — recommends the ESLint / Prettier / EditorConfig extensions

When you pull a newer version of this package, re-run with --force to refresh the files.


Part of the bluehop toolkit — a set of shareable project configs. Best alongside bluehop-eslint-config and bluehop-prettier-config, which the editor settings are tuned for.