Join egghead, unlock knowledge.

Want more egghead?

This lesson is for members. Join us? Get access to all 3,000+ tutorials + a community with expert developers around the world.

Unlock This Lesson
1×
Become a member
to unlock all features

Level Up!

Access all courses & lessons on egghead today and lock-in your price for life.

Autoplay

    Prepare a Custom React Hook to be Published as an npm Package

    Joe PreviteJoe Previte
    reactReact
    ^16.8.6

    Before we publish our package, we want to make sure everything is set up correctly. We’ll cover versioning, preparing our package, adding a proper README, and updating our package.json.

    Code

    Code

    Become a Member to view code

    You must be a Member to view code

    Access all courses and lessons, track your progress, gain confidence and expertise.

    Become a Member
    and unlock code for this lesson
    Discuss

    Discuss

    Transcript

    Transcript

    Instructor: To prepare a custom hook to be published as an npm package, we're going to walk through a few things we need to do, the first of which is make a few changes in the package.json. We'll start with the version key. You'll notice that, right now, it says 1.00That's because that's how the boilerplate set it up for us.

    However, we're going to change that to 000The reason that we're doing that is because, instead of manually bumping the version, we're going to use an npm CLI command called npm version. Npm version is a handy utility provided by the npm CLI to bump a package version.

    You're probably wondering, "What's the point of using a CLI tool to bump a version? Can't you just do it manually?" You could, but you'll notice here it says, "If run in a git repo, it will create a version commit in tag," and that's what we want.

    You'll notice the npm version takes one argument of new version, which can be any of the following. It'll automatically update the package.json, the package-lock.json, and if you have it in in npm-shrinkwrap.

    Before we can use the npm version command, we need to make sure that we have a clean git working directory. I'm going to commit this change we made to the package.json. Now let's go ahead and run npm version major. You'll notice that it printed the version, and it updated it in our package.json as it said it would. If we run git tag, we'll see that we have a new commit tagged, v1.00The next thing we're going to do is take a look at the scripts section. One thing I want to point out is a script that was set up by the boilerplate called prepare. What it does is it runs this command before it goes through with the npm publish.

    What happens is we run npm publish. The npm CLI checks your scripts. It looks for a prepare script. If it sees one, it'll run this before publishing your package. In our case, it's running yarn builds, which builds our project using rollup. This is handy because it prevents you from accidentally making changes and forgetting to run yarn build before publishing your package.

    We're going to add in one more script at the bottom. We're going to add the script postpublish. What it's going to do is run git push --tags. As you can imagine, this will run after the publish command has finished. We add this because we're going to use the npm version CLI to bump the version, which will create a new tag. Then when we run publish, after it's done, it will push our tags to version control.

    Another change we'll make is here in the peer dependencies. The peer dependencies are the packages that are required by our package in order to make sure it works properly. Since our package is a custom React hook, we want to make sure that the user has React in their project.

    We don't necessarily need this exact version so we're going to change this and instead, use the "greater than or equal to" which says, "Hey, we want a version that's greater than or equal to 16.8.6." The last thing we'll do in our package.json, scroll down to the bottom. We're going to add a new key called publish.config.

    It's going to have a key called access=public, with a lowercase p. The reason that we add this in is because there's two types of packages. There are public packages and private packages. Private packages are a paid feature of the npm registry. By default, scoped packages, so ones that start with the "and" sign in the username are private by default.

    We need to tell nmp, "Hey, this is a public package." We do that by adding this in. That's all for the package.json. The last thing we're going to do is update our README that's at the root. You'll notice that the boilerplate filled out most of this for us. The one section that needs to be updated is the usage section.

    You'll notice that it still has the boilerplate code from when we initialized the project. What we're going to do is go inside the act.js inside of example/source. We're going to copy this and paste it in in this JSX block. This is important because after we publish the package, npm will look at the root and use the README on the package detail page.

    That's all you need to do to prepare your package to be published on npm.