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-meta

v1.0.0

Published

Generate json file subset of key value pairs from package.json

Downloads

5

Readme

package-meta Build Status npm

Generate json file subset of key value pairs from package.json

Problem

In a browserify/webpack/etc environment, it's possible that a developer may erroneously include the entirety of package.json in the client side assets because they need to get some simple value like the package name or version.

Solution

Create a subset of the key value pairs from package.json and save it as a new file which can be required. This should be during your prepublish step by adding a script to your package.json "prepublish": "node bin/package-meta keys=name,version"

Arguments

| Argument | Default | Description | |-|-|-| | cwd | process.cwd() | The current working directory from which the package.json file is read and the new meta file is written | | keys | '' | A comma separated list of keys of fields to extract | | out | 'package-meta.json' | The name of the new file to save the extracted data. Can be a relative path like './meta/package.json' |