DEV Community

Cover image for I've made my first NPM package. Why haven't you yet ?
Alessandro Cipolletti
Alessandro Cipolletti

Posted on

1

I've made my first NPM package. Why haven't you yet ?

Until not so long ago, every new project of mine always started with a copy/paste of some utils.js file I made in the past.

I'm sure I'm not the only one, and I'm sure most of you are lazy enough (like I was) to keep doing that instead of what you should do: putting that code in a standalone library.

First of all, code evolves during time
Sometimes I needed to update that code I just copied to take care of a new edge case, and at the end I found myself having multiple versions of the same functions.
And this without even considering bug fixes...

Second, this made me a better developer
Knowing that those functions could eventually evolve in the future inside other projects, I never took the time to rewrite them in typescript or write for them a good documentation.

Third, I learned something new during the process
This was my first Npm Package. I learned something new doing it. Isn't this always a win?

So better code, new skills, and why not a new line to put on the cv.

I'm almost proud of the documentation I've put together for my code, so I'm sharing it with you guys:

Npm: https://www.npmjs.com/package/js-math-and-ui-utils
GitHub: https://github.com/AlessandroCipolletti/my-js-math-and-ui-utils

rick almost proud

PS: I'm not putting here any tutorial link. I bet you all know how to use google.

AWS Security LIVE!

Join us for AWS Security LIVE!

Discover the future of cloud security. Tune in live for trends, tips, and solutions from AWS and AWS Partners.

Learn More

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay