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

package-resolve

v1.2.4

Published

Simple way to get the package.json for any installed package.

Downloads

12

Readme

package-resolve

Simple way to get the package.json for any installed package.

This finds the package.json for any package installed in node_modules so that if can be accessed by the running server.

It can also find the main key and a style key as well as returning the package.json as an object or the css as a string.

This package uses native Promises throughout.

Install

npm install package-resolve

Example

The example is based on having installed bootstrap. It does not need to have been required.

Pack = require('package-resolve');
pack = new Pack('bootstrap');

pack.package()
.then (file) =>
  // file contains the path of the package.json file
.catch (err) =>
  // err contains a descriptive error such as "File not found"

Usage

new

Pack = require('package-resolve');
pack = new Pack(<package to find>);

This should be passed the name of the package to find as listed under dependencies in our package.json.

package

pack.package()
.then (file) =>
  // file contains the path of the package.json file
.catch (err) =>
  // err contains a descriptive error such as "File not found"

This returns a Promise that resolves to the full path of the package.json file for this dependency.

resolve

pack.resolve()
.then (file) =>
  // file contains the path of the `main` file in the package.json
.catch (err) =>
  console.error(err);

style

pack.style()
.then (file) =>
  // file contains the path of the file referred to in the style key
.catch (err) =>
  console.error(err);

readPackage

pack.readPackage()
.then (obj) =>
  // obj contains the contents of package.json as an object
.catch (err) =>
  console.error(err);

readStyle

pack.readPackage()
.then (css) =>
  // css contains the css as a string
.catch (err) =>
  console.error(err);

Problems

Any issues or comments would be appreciated at Github

Pull requests are welcome.