Sounds good! Cheers :) Axel Chandelier

Nice guide! I'm not a noob, but I just thought I'd recommend to add a small section on npm link and npm pack which will allow the author to first test their npm package locally before publishing to npm registry. No fun to publish a package just to learn it won't install :)

I'm a sort of mixed bag haha. Probably more introverted with the ability to muster up some courage to do crazy things like get on a stage and perform (but then go retreat to my cave again lol) Annie 🦄⚡

You know, I just did this a few days back and then completely overhauled it to use @nrwl/nx which is quite handy in terms of generating really nice angular configuration. I took notes here The reason I preferred this, is you get things like Storybook configuration, dg analysis, etc., etc., all for free. That said, using this approach here is certainly viable! One thing I would recommend though is to npm link and test the package locally first before publishing. Or, npm pack and install it locally to do the same. It's not fun to publish to the registry just to learn your package won't install.

Really helpful tutorial Adithya. I gotta write one of these at work today and your tut very easy to understand!

Just learned a new word ambivert ; I can relate to that!

This post was unique from what I've read so far as a Hashnode noob. It was refreshing to see some photos and selfies and a travel / conference based topic. Congrats on speaking at the 2 conferences and thanks for sharing your journey!

Why is "User friendly" in the cons bullet? Are you saying that the maintainer has to invest time to be friendly to the library/framework users and contributors? Or, open source libraries aren't generally as user friendly as commercial? Or aren't required to be?

Your next article needs to be: "How to NOT write a good title for your post. Not!"; definitely a clever title haha. I would add, writing needless comments to blog posts as another way to NOT be a good programmer…oh shit, I'm using my open source time to putz around writing comments haha!

Lovely extensions list! Be careful with import cost…it has a cost :) My buddy at work spent a while troubleshooting why his vscode had bogged down. The premise of this plugin is really great and important, but when you think about the work it has to do to glean those sizes for you, I'm not sure I want that in my editor. Of course, I came from using ST3 and vim when vscode finally felt like the one IDE that wasn't a hog. For me, bundlephobia on demand is how I will have to roll. I would add indent-rainbow and webhint to this already great list!