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

pkg-edit

v1.1.4

Published

Modify software information after packaging with [pkg]

Downloads

6

Readme

Modify software information after packaging with pkg

how to use

  1. Introduce pkg-edit in the current project: npm i -D pkg-edit

  2. Initialize configuration information (only needs to be executed once): npx pkg-edit init, It will generate a pkg.config.js in your project

    module.exports = {
      // You need to pay attention to this, this is the exe file generated by pkg
      file: "./release/build.exe",
      // ...
    };
  3. You can edit your package.json like this:

    {
      // ...
      "scripts": {
        "build:win": "pkg -t win -o release/build.exe src/index.js && pkg-edit build"
        // pkg saves the exe file to release/build.exe, pkg-edit will read and modify it according to the configuration
      }
      // ...
    }

can also be used like this

  1. Execute npx pkg-edit init in the project directory
  2. You can view pkg.config.js and modify some predefined configurations. You must specify the file field to point to the exe packaged by pkg
  3. Execute npx pkg-edit build, it will generate a new exe file according to the content of pkg.config.js