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

@wns-test/wns-test-ms

v1.0.5

Published

## Initialization and manual publish

Downloads

8

Readme

Publish a npm package

Initialization and manual publish

Initialize and first publish

  • initialize a new npm project
npm init -y
  • change the name in package.json to @organization/project
  • initialize git repository and commit
  • publish your package
npm login
npm publish
  • check your profile on https://www.npmjs.com/

Write a typecript package

  • create tsconfig.json
tsc --init
  • install dependencies
npm install typescript del-cli --save-dev
  • create src/index.ts with some ts code
  • update tsconfig.json
{
    ...
    "declaration": true,                   /* Generates corresponding '.d.ts' file. */
    "outDir": "./build",                        /* Redirect output structure to the directory. */
    ...
}
  • update package.json scripts to be sure to clean the build directory
{
    ...
    "scripts": {
        "clean": "del .build/*",
        "build": "npm run clean && tsc"
    },
    ...
}
  • make sure to gitignore build/

  • fill main, types and files in package.json

{
  ...  
  "main": "./build/index.js",
  "types": "./build/index.d.ts",
  "files": [
    "./build/**/*"
  ],
  ...
}

Update and publish new package version (manually)

  • commit your changes
  • update your version number manually or run command:
npm version patch
  • build and publish
npm run build
npm publish

Publish automatically with a Github action

Connect to a remote github repo (if not done yet)

git remote add origin [email protected]:**github-account**/**project-name**.git
git branch -M main
git push -u origin main

npm publish token

  • create and copy a npm publish access token
  • create a repository secret NPM_TOKEN on your Github repository

Create a publish action

  • copy .github/workflows/publish.yml in you repository
  • before pushing to main think of update the package version