fix the inconsistency in Development start command between Contributing Guide and README

[TenzDelek]

Description

The inconsistency between the Contributing Guide and the README regarding the development start command appears to be a result of the project's migration to Turborepo. To ensure clarity and consistency for contributors, it would be beneficial to align the documentation across all project files.

Related Issues

Fixes #7219

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Nov 13, 2024 4:38am

[mikeesto]

I think we probably want to keep the command as npm run dev (since that's the common way of starting the dev process in JS projects) and update the README to match instead?

[TenzDelek]

I think we probably want to keep the command as npm run dev (since that's the common way of starting the dev process in JS projects) and update the README to match instead?

thank you for pointing that out, I should have take a deeper look at the package.json (where the dev script was implementing the turbo command) which @AugustinMauroy did point out (#7219 (comment)). got confuse a little bit 😃

[mikeesto]

LGTM, thanks