Recently I decided to create my first NPM package. I was inspired to do this after spending some time to finally get eslint and Prettier fully set up for my projects. I started by following the video below from Wes Bos about setting up eslint and Prettier in VS Code.
Forking The Repo
The first thing I did was to fork Wes’ repo and add the additional sections and changes that I wanted for my projects. I also updated the package name, author and repo details in the package.json and package-lock.json files.
Creating a Package
Next up was to research how to publish packages to NPM. The first thing I did was to check YouTube to see if there were any good tutorials for this. I was lucky to find the video below from Gary Simon, that showed the full process from writing some code to publishing the package.
The NPM Process
For the vast majority of the process from signing up to NPM and publishing my package, the process was very smooth and straight forward. The only issue I ran into was the package being denied because its name was triggering a spam error. In my original package name, I wanted to use my full GitHub user name, but this would not work. So I changed the package name to something close to what I wanted but not quite as clean as I would have liked it to be.
After this, I spent some time reading various posts online via Stack Overflow and other forums and found that the numbers at the end of the package could be the reason for the spam flag being triggered. So, in the off chance that this was what was causing the issue, I decided to drop the numbers and try to publish a new package with this new name. To my surprise this worked, it wasn’t exactly what I wanted the name to be but it was a lot better than the one I was currently using.
Using the Package
eslint-plugin-html Not Working
The first issue I had with the package was errors with the eslint-plugin-HTML package not working. Thankfully after looking at some GitHub issues, I found that upgrading the package to version 6.0.0 would fix the problem and it did.
React Version Detect Issue
The next issue with the package I ran into was an error where the eslint-plugin-react package was not returning the react version. This issue caused me to scratch my head quite a few times trying to find the exact cause of the issue and get a fix for it.
I spent a good bit of time searching online, reading docs and checking posts that might have something to do with this issue. But after looking everywhere I could think of I simply tried updating the package to the latest version and that fixed my issue.
Was it worth the time? Yes, I always enjoy learning and doing new things when it comes to coding. So creating an NPM package of my own after using an assortment of different packages to do various things in personal, educational and professional projects. It felt good to create one of my own.
It also allows me to update my eslint and Prettier settings to suit my needs and gives me access to dive into the finer details of the tools I am using. As well as giving me the experience and knowledge to be able to create more packages in the future for things I find useful and want to easily share and reuse.