# Command to change folder names by moving everything It’s also a good idea to update the folder name as well for consistency. (You can check for naming collisions by doing a search on npm, or through the npm search command). To change your package name, you change the name property in the package.json file. If the package already exists on npm (because your package has the same name as another package on npm), you won’t be able to publish it. The final step is to publish your package with the npm publish command. (Feel free to skip questions that don’t make sense). This package.json file contains the bare necessities you need to publish your project. This command runs you through a few questions and creates a package.json file for you at the end.

Next, you want to begin the project with the npm init command. The command line version is: # Creating a folder named how-to-publish-to-npm To do so, create a folder somewhere on your computer and navigate to it.

You’ll be prompted to enter your username, password, and email address. (You need to have Node and npm installed on your system before you perform this step.

Second, you need to login to your npm account through the command line. Create one here if you don’t have one yet. To publish your first package to npm, you need to go through these steps:įirst, you need to have an npm account. Feel free to skip to the next section if you’ve published one before. This section is for you if you haven’t published a package to npm before. We’ll go through what steps are required, and I’ll show you an easy way to publish and update your package. There are two steps:īut publishing packages the way the industry does it? Not so simple. It’s simple to publish a package onto npm. How to publish packages to npm (the way the industry does things) 20th Mar 2019

Package npm