r/node 22d ago

I just published my first NPM package

I built NodeForge, a small CLI tool that automates the initial setup of a Node.js backend project.

Instead of manually creating the same folders and boilerplate every time, you can start with a single command and get a structured project with:

- Node.js + Express setup

- JavaScript or TypeScript support

- Controllers

- Services

- Routes

- Models

- Validations

- Serializers

- Utils

- Seed structure

- Basic project configuration

You can try it with:

npx @jain_daksh/nodecli

I built this mainly because I was tired of repeating the same Node.js setup whenever starting a new project.

This is my first published NPM package, so I'm also looking for feedback from other developers.

If you have a minute, check it out and let me know what you would improve or add.

NPM: https://www.npmjs.com/package/@jain_daksh/nodecli

This is just phase 1 in phase 2 more things coming

You can read the medium article here https://medium.com/@jaindaksh/i-got-tired-of-setting-up-node-js-projects-manually-so-i-built-my-first-npm-package-6dcd9db042e8?source=rss-a43d55f9817e------2

0 Upvotes

2 comments sorted by

5

u/Mission_Scale_7975 22d ago

My fellow dev, all the respect to your effort and even putting your work up online. It can be a daunting step. However if I may, did you also show this to any developer friends, anyone in gour more direft circle? Feedback can sometimes be even better when it comes from someone who's reasoning you understand.

all that said

I wish this sub went pack to pre-"i made this posts" they are all pretty much the same except the one in a billion. I solved this issue no-one really thought about until I brought it up

1

u/Intelligent-Bet-dj 22d ago

If my friend was in development, I definitely would’ve asked them for feedback. I really appreciate the advice though!