How to write and publish your first Typescript library

If you keep creating the same blocks of code over and over it might be a good idea to turn them into reusable modules. There is nothing more modular when it comes to code than writing a library. But where do you start. In this video I will show all you need to write and publish your first Typescript / Javascript library as an NPM package
Table of Contents:
00:06 - Check if library name is available
00:41 - Create your new library folder
01:07 - Create a package.json file
01:27 - Add essentials values to package.json
02:04 - Install typescript
02:18 - Create dynamically a tsconfig file
02:45 - Add essential values to tsconfig
04:10 - Add your lib files under a src folder
05:43 - Convert typescript to javascript
06:08 - Login to npm via the cli
06:36 - Now publish your package
07:05 - Time to test your new package
09:32 - How to test without adding a new version
13:43 - Next steps

[@erikjohnson9112]

Wow, you covered EXACTLY what I wanted. Well done. Thanks!

[@AdyNgom]

glad it was helpful - thank you for the comment

[@k1defjoel397]

Very well organized presentation, getting right to the point and not having the viewer jump through the hoops and loops of "oh let's start out by making mistakes!" Bravo!

[@AdyNgom]

thank you for the kind remarks Joel. Glad you found it useful :)

[@ironsand]

GREAT content! It was exactly what I needed but had trouble finding. Thank you!

[@ryanclements6272]

im so glad this exists! I really wish I had this when I was trying to build my first npm package.

[@AdyNgom]

Awesome glad you find it useful. Cheers

[@edwardliemingwong7683]

Great video, Ady!

[@AdyNgom]

thank you kindly

[@fode-diop]

Saved je so much time. Thank you! 🔥

[@AdyNgom]

glad it did - thanks for the comment :)

[@VinceTaneri]

Really helpful, thanks!

[@AdyNgom]

You welcome 🙏🏿 happy you found it helpful

[@anilrajan100]

Very good video, one thought is instead of link library, if we use monorepo or turbo its combine all apps and its dependency using namespaces

[@subhranshudas8862]

Great compact video! I always had a doubt about should we bundle the TSC generated files in dist, before publishing them to NPM?

[@thanhnv10]

I can do it Thank you so much

[@ngatcharius]

Good Job 👍🏾 Thanks

[@AdyNgom]

Thank you glad you like it 🙂

[@user-ty6vq8xy9m]

nice

[@memories1641]

Thank you

[@AdyNgom]

you are very welcome :)

[@goodylili]

good one

[@AdyNgom]

Thank you! Cheers!

[@ironsand]

When I created a npm link to my project, it imports brings to node-modules everything in the linked package, including source folder and configuration files. How can I link only the dist folder?

[@kalanibright9236]

I've never seen anyone include typescript in normal dependencies and not --save-dev...just fyi ...should probably be the other.

[@AdyNgom]

Hello Kalani. I think a more accurate statement could be we might not need to include Typescript in the normal dependencies since the library final output is vanilla JS and I completely agree. I just tend to shy away from word like "never" because they can be very limiting. In the case of the Angular framework for example, Typescript is a core dependency as in many others. This is intended to show the different steps needed to publish a library to NPM. Feel free to add more to it and I'll happily link to that content. Thank you for the feedback :)