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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@circlehq/email-builder

v0.0.6

Published

CircleHq Email Builder component

Readme

circlehq/email-builder

How to Publish a React Package to npm

This guide explains how to set up, build, and publish a React package to npm using Babel.

Prerequisites

Make sure you have the following installed:

  • Node.js
  • npm
  • Babel

1. Initialize Your Package

Start by creating a package.json file for your project if you don't have one already:.

  1. Prepare Your Package Before publishing, ensure you have a package.json file in the root of your project. You can create one by running:
npm init

This will prompt you for information such as the package name, version, and entry point. Make sure to fill it out correctly.

1.1 Package Name

  • For a public package, use a unique name, e.g., your-package-name.
  • For an organization package, use a scoped name, e.g., @your-org/your-package-name.

1.2 Add a Build Script (Optional)

If you are using TypeScript, Babel, or another compiler, add a build script in your package.json:

"scripts": {
  "build": "your-build-command",
  "prepublishOnly": "npm run build"
}

This ensures that your package is built before publishing.

2. Add an .npmignore File

Create a .npmignore file to exclude unnecessary files from your published package. Common exclusions include:

/node_modules
/tests
/src
/*.log

This prevents unnecessary files from being included in the npm package.

3. Login to npm

If you are not already logged in, log in to npm using:

npm login

You'll be prompted for your npm username, password, and email.

4. Publish Your Package

To publish your package to npm, run:

npm publish

For scoped packages (e.g., @your-org/your-package-name), you must specify public access:

npm publish --access public

5. Update Your Package Version

To update and publish a new version of your package:

  1. Update the version in package.json (e.g., from 1.0.0 to 1.0.1).

  2. Run the build script, if necessary:

    npm run build
  3. Publish the updated package:

npm publish

For scoped packages (e.g., @your-org/your-package-name), you must specify public access:

npm publish --access public

6. Verify the Package

You can verify that your package was published successfully by checking it on the npm website:

npm info your-package-name

Or visit npmjs.com and search for your package.

By following these steps, you will successfully publish your package to npm.

7.Updating Your Package

When you need to publish an updated version of your package:

Increment the version in package.json.

Rebuild the package:

npm run build

Publish the updated package:

npm publish

Conclusion

By following these steps, you will be able to successfully publish your React package to npm. Don't forget to update the version each time you make changes and republish!