fix: update libnest-dev script be be POSIX-compliant

[joshunrau]

Summary by CodeRabbit

• New Features
  • Enhanced command-line execution with automatic source-map support for improved debugging.
  • Introduced a new flag to disable the auto-watch functionality, giving users better runtime control.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates a Node.js CLI script by changing the way command-line arguments are processed. It removes the WATCH_FLAGS variable and introduces a new NODE_FLAGS variable, which includes the --enable-source-maps flag. Additionally, it adds a boolean NO_WATCH variable (defaulting to false) that is set to true when the --no-watch flag is detected. This change modifies the conditional logic to append --watch and --watch-preserve-output flags only when NO_WATCH is not active. Finally, the script executes the Node.js command with the updated flags and the original arguments.

Changes

File(s)	Change Summary
src/cli/.../libnest-dev	Removed WATCH_FLAGS. Added NODE_FLAGS (with --enable-source-maps) and NO_WATCH. Updated argument parsing to check for --no-watch flag and conditionally append watch flags before executing the Node.js command with "$@".

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant S as CLI Script
    participant P as Argument Parser
    participant N as Node.js Executor

    U->>S: Run CLI command with arguments
    S->>P: Parse command-line arguments
    alt '--no-watch' flag detected
        P->>S: Set NO_WATCH = true
    else No '--no-watch'
        P->>S: Append --watch & --watch-preserve-output to NODE_FLAGS
    end
    S->>N: Execute Node.js with NODE_FLAGS and original args ("$@")

Loading

Poem

I'm a bouncy rabbit with a flair so neat,
Hop-scotching through flags on nimble feet.
Goodbye to WATCH_FLAGS, it's time to change the tune,
NODE_FLAGS now shine like a bright full moon.
With a whisper of "--no-watch", I decide my race,
Coding in rhythm at a gentle pace.
Join my merry hop as we update this space! 🐇✨

---

📜 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 3efcb9a and 03b7009.

📒 Files selected for processing (1)

• src/cli/bin/libnest-dev (1 hunks)

---

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.

[github-actions]

🎉 This PR is included in version 4.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀