docs: changed node and npm version in Development.md to a compatible version

[pseudo-tensor]

Fixes: #1456

The minimum node and npm versions will be changed to the ones being used by docker, i.e., node: 18.20.8 and npm: 10.8.2 which works as expected.

Summary by CodeRabbit

• Documentation
  • Updated troubleshooting guidance with revised minimum version requirements for Node.js (now 18.20.8 or higher) and npm (now 10.8.2 or higher).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1e5ffd5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The pull request updates the troubleshooting section in the Development.md file by increasing the minimum version requirements for Node.js and npm. Node.js now requires version 18.20.8 or higher, and npm requires version 10.8.2 or higher. No changes were made to the exported or public entities.

Changes

File(s)	Change Summary
Development.md	Updated troubleshooting section: Node.js version increased from 18.12.0 to 18.20.8 and npm version from 8.19.0 to 10.8.2

Possibly related issues

• [Docs Bug 🐞 report]: minimum node version specified in Development.md does not work. #1456: Updates to the minimum version requirements address the reported bug related to outdated Node.js and npm specifications in the Development.md file.

Suggested labels

ready-to-merge

Suggested reviewers

• Florence-Njeri
• asyncapi-bot-eve
• derberg

Poem

I'm a bunny, hopping with cheer,
Updating docs to make it clear.
Node and npm now leap to new heights,
Hopping past old errors into brighter lights.
With every change, my heart delights! 🐰🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 591741f and 5ff4034.

📒 Files selected for processing (1)

• Development.md (1 hunks)

🔇 Additional comments (1)

Development.md (1)

187-191: Updated Version Numbers are Correct and Clear
The updated minimum versions for Node.js (18.20.8 or higher) and npm (10.8.2 or higher) are clearly stated and align with the versions used in the Docker environment. This change improves consistency in the development setup documentation.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[derberg]

why 18.20.8?

[pseudo-tensor]

it's the node version being used in the docker image in the repo so that way there will be consistency in the node version in local setup and in the docker container

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud