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

@igorskyflyer/editorconfig

v1.0.0

Published

✍🏼 A CLI tool for adding an opinionated EditorConfig to any project. 🐭

Readme

Table of Contents

Features

  • 🎨 Copies .editorconfig into the current project instantly
  • ⚠️ Detects existing .editorconfig and prompts before overwriting
  • ⏭️ Skips safely on declined overwrite - no destructive changes
  • ✅ Clear success and error feedback for every outcome
  • 🛡️ Zero dependencies - pure Node.js built-ins only

Usage

Run it directly without installing:

npx @igorskyflyer/editorconfig

Or install globally:

pnpm add -g @igorskyflyer/editorconfig
npm i -g @igorskyflyer/editorconfig
yarn global add @igorskyflyer/editorconfig

Then run:

editorconfig

Adding .editorconfig to a fresh project:

✅ .editorconfig added to the project!

Running in a project that already has .editorconfig:

⚠️ .editorconfig already exists. Overwrite? (y/N)  

Accepting the overwrite:

✅ .editorconfig updated successfully!

Declining the overwrite:

⏭️  Skipped.

Implementation

The CLI resolves two paths at runtime:

  • source - the .editorconfig bundled inside the package
  • destination - the current working directory (process.cwd())

If no .editorconfig exists at the destination, it is copied instantly. If one already exists, an overwrite prompt is shown before any changes are made. All errors are caught and displayed with a non-zero exit code, ensuring shell scripts and CI pipelines can detect failures.

Configuration Decisions

  • end_of_line = lf - Unix line endings are the cross-platform standard for source code. Git, Linux, and macOS all default to LF, and most tooling (ESLint, Prettier, Biome) expects it.
  • *.{bat,cmd,ps1} = crlf - Windows scripting formats require CRLF. The Windows script host and some parsers behave unexpectedly with LF-only line endings in these files.
  • *.sh = lf - Shell scripts break on CRLF. The Unix shebang line (#!/bin/bash) must be LF-terminated or the interpreter fails to parse it.
  • *.go = tab - gofmt enforces tabs. Fighting it is futile and breaks the whole Go toolchain.
  • trim_trailing_whitespace = false for *.md - Markdown uses trailing spaces as intentional line breaks (\n). Trimming them silently breaks formatting.
  • insert_final_newline = true - POSIX defines a text file as ending with a newline. Omitting it causes noisy diffs and warnings in many tools.

Motivation

Manually copying .editorconfig across projects is repetitive and error-prone. A shared, versioned config ensures every project stays consistent - one update propagates everywhere, just like all packages of the @igorskyflyer ecosystem do!

Changelog

Read about the latest changes in the CHANGELOG.

License

Licensed under the MIT license.

Support

Related

@igorskyflyer/valid-path

🧰 Determines whether a given value can be a valid file/directory name. 🏜

@igorskyflyer/windows-packages

💻 A package for reading the Packages registry key on Windows 10+. Useful for retrieving Windows 10+ installed Store applications. 📦

@igorskyflyer/astro-render-component

🤖 Astro component renderer. Zero configuration. Produces clean HTML strings directly in Node.js without any DOM environment. 🐬

@igorskyflyer/my-file-path

🌟 A package that strongly types file paths! 🥊

@igorskyflyer/common-types

🔦 Provides frequently used types for your TypeScript projects. 🦄

Author

Created by Igor Dimitrijević (@igorskyflyer).