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

pika-plugin-package.json

v1.0.2

Published

@pika/pack build plugin to modify package.json file

Downloads

73

Readme

pika-plugin-package.json

Build Status Coverage Status License NPM Made with Love

@pika/pack build plugin to modify package.json file.

Install

$ yarn add --dev pika-plugin-package.json

Or using npm

$ npm install --save-dev pika-plugin-package.json

Usage

{
  "name": "example-package-json",
  "version": "1.0.0",
  "@pika/pack": {
    "pipeline": [
      // ---8<---
      [
        "pika-plugin-package.json",
        {
          "+dependencies": {
            "lodash": "^"
          },
          "*keywords": ["+example"],
          "*files": ["-bin/"],
          "+author": "^",
          "-devDependencies": {}
        }
      ]
    ]
  }
}

Options

Pass any object, and it will be merged to result pkg/package.json There are three modifiers, which you can add to properties / array items:

  • -: remove this property / item
  • *: merge this property (if there is no such property - it will be added)
  • +: add this property / item (if already exists - it will be replaced)

By default (without modifier) - merge (*) is applied. But I recomment always define modifiers for more expressness and clarity.

If you want, for some reason, add property named *prop (for example) — you can escape modifier like this - \\*prop - or just explicitly define needed modifier - +*prop - as I recommended before.

For example

"+license": "MIT" will add (or replace) license field.

"-devDependencies": {} will remove devDependencies (value is not really matters here).

"*dependencies": { "lodash": "^4.17.15" } will add lodash dependency to existing dependencies (or will create dependencies with lodash, if there were no any dependencies).

"*files": ["-bin/"] will remove bin/ item from files property.

Inheritance

You can specify special value ^ to any property, and value will be populated from original package.json. For example:

"+author": "^" will add author field with value from original package.json (if defined).

This should work on any deep level, but only with object properties (no arrays).

Real world example

You can check this package's package.json, I use pika-plugin-package.json in pipeline to modify pika-plugin-package.json's package.json ^_^

Sponsored