The latest articles on DEV Community by Mennatulllah (@mennatulllah). https://dev.to/mennatulllah https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F369758%2F7569a73b-0533-4f8b-af4f-e45cf2c1ea41.png https://dev.to/mennatulllah en Mennatulllah Sun, 19 Apr 2020 15:57:40 +0000 https://dev.to/mennatulllah/quick-reference-to-create-and-publish-your-npm-package-2bga https://dev.to/mennatulllah/quick-reference-to-create-and-publish-your-npm-package-2bga <p>1- first step if you don't have an npm registry account, you can sign up from : <a href="https://www.npmjs.com/signup">https://www.npmjs.com/signup</a> or use command: npm adduser </p> <p>(note: it's better to signup using the site url in order to solve errors of available usernames, password complexity ..etc)</p> <p>2- verify the account</p> <p>3- npm login </p> <p>4- fill in the conditionals</p> <p>5- mkdir "package-name"</p> <p>6- cd "package-name"</p> <p>7- npm init<br> (note: if you want to make it scoped to specific organization or user account (private packages) you should use this init command with the scope flag (eg: npm init --scope=@user-name) and this feature for paid accounts only)</p> <p>8- now you can test the package locally by running command : npm i "package-name"</p> <p>9- npm publish <br> (note: you may have to change the package name if you get publishing error because of name duplication)</p> npm typescript angular node