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

@optimics/npm

v0.8.5

Published

Bindings for often used npm functions

Downloads

5

Readme

@optmics/npm

Useful methods that extend npm functionality

Method collection

urlToPath(url: string): string

Translate the url using fileURLToPath when it contains url prefixed with protocol, otherwise it return the url unchanged, assuming, it is a file path.

urlToPath('file:///home/user/test.js')
// /home/user/test.js

urlToPath('/home/user/test.js')
// /home/user/test.js

urlToCwd(url: string): string

Translate url to nearest directory path.

urlToPath('file:///home/user/test.js')
// /home/user

urlToPath('/home/user/')
// /home/user

urlToPath('/home/user')
// /home/user

getRoot(cwd?: string): string

Return monorepository root. The directory, that contains your root package.json.

getRoot()
// /home/user/path/to/monorepo

filterUnique(item: T, index: number, src: T[]): boolean

Array helper method, that filters unique elements

[1,2,2,3].filter(filterUnique)
// [1,2,3]

extractProjectScope(p: PackageJson): string

Extracts the project scope from the package.json manifest.

'@myscope/mypackage' -> '@myscope'

extractPackageName(p: PackageJson | string): string

Extracts package name from the package.json manifest or package name.

'@myscope/mypackage' -> 'mypackage'

padScope(scope: string): string | null

Append at sign ('@') to the project scope, if it is missing

'myscope' -> '@myscope'

getPackages(cwd?: string, options: GetPackagesOptions = {}): PackageJson[]

Get manifests of all packages defined in the monorepository.

getPackageNames(cwd?: string, options: GetPackagesOptions = {}): string[]

Get list of all package names defined in the monorepository.

getPackageScopes(cwd?: string, options: GetPackagesOptions = {}): string[]

Get list of all package scopes defined in the monorepository.

getPackageJsonByName(cwd: string, packageName: string): PackageJson

Get package.json by package name.

readPackageJson(cwd: string): PackageJson

Read package JSON in a directory path.