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

import-sorter

v1.0.0-alpha.6

Published

An opinionated ES6 and TypeScript import sorter.

Readme

Import sorter

An opinionated ES6 and TypeScript import sorter.

TODO:

Ts config json

  • Should we include dom in lib?

Docs

  • write a dev guide how to develop:
  • yarn install
  • yarn watch (will block one terminal tab)
  • whenever you make a change, it will automatically be picked up by tsc
  • Quick and dirty way to run cli version: ./node_modules/.bin/ts-node ./bin/index.js
  • yarn build:prod for a production build
  • To test the newest library (not yet published) in another project, do yarn link. Then, in the other project run yarn link import-sorter. After this, you will be able to
import { sortImports } from 'import-sorter';
const result = sortImports(...);

After testing, make sure to unlink import-sorter, by navigating to it and yarn unlink

Debugging the CLI

  • Temporarly add a call to cliSort function in src/cli/index.ts with a desired configuration, i.e.:
cliSort({
  content: '',
  dryRun: true,
  verbose: true
});

Note - in this way, the configuration binding is being skipped, and it can't be relied on the default value. Thus, all desired configuration value have to be explicitly specified.

  • Use the VSCode's launch.json and launch the Launch Program configuration

Future

  • An option to specify a path or a file(s) in which to sort imports. If no option is specified, run on all files.
    • Maybe use this: https://nodejs.org/api/path.html#path_path_isabsolute_path
    • We can maybe use one files argument, which can be an array of either directories or files. If it's a file, run the lib on it. If it's a directory, run the lib on the files inside it. Optionally, if recursive flag is up, continue to iterate through directories recursevly