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

jnpkg

v2.2.0

Published

npm module packing tool

Downloads

18

Readme

semantic-release Package Quality license GitHub commit activity npmsio final GitHub Release Date Security Rating Reliability Rating Coverage Snyk Vulnerabilities for npm package GitHub Workflow Status CircleCI

This is a node module packaging tool, which supports Typescript and Standard Javascript languages.

Table of Contents

Background

To publish multiple modules to NPM, it is best to have a common packaging tool that automatically exports CJS version and standard ESM version, as well as type support.

Installation

# local
npm install --save-dev jnpkg
# global
npm install -g jnpkg

Usage

Use the jnpkg init command to generate the package.json file.

Set main and module to distinguish between CJS and ESM, which is conducive to the optimization of users when packaging.

The watch mode will be automatically packaged to the target according to the modification of the source file.

{
  "main": "lib/index.js",
  "module": "es/index.js",
  "scripts": {
    "watch": "jnpkg watch",
    "build": "jnpkg build"
  }
}

We put the source files into the src folder of the root directory. (E.g. ./src/index.ts).

Then running npm run build will generate cjs (lib directory) and esm (es directory) in the root directory.

Finally, we can publish to npm normally through the npm publish command.

Or you can set semantic-release to automatically publish to npm.

The jnpkg init command automatically generates semantic-release related files.

NPM Token and GITHUB Token can refer to the following URL

https://github.com/settings/tokens

https://www.npmjs.com/settings/{username}/tokens

Setting

// .jnpkgrc
{
  "lib": true, 
  "es": true,
  "browser": true,
  "pkgName": "pkg",
  "entry": "./src/index.ts",
  "binEntry": ["./src/index.bin.ts"], // only cli build mode
}

Maintainers

JuLong - jl917

Contributing

Anyone is welcome to participate in the maintenance and development of this project, and can also submit Issues and PR's

License

MIT