fix: remove shebang from npm bin scripts for better compatibility

[ymc9]

Summary by CodeRabbit

• Chores
  • Updated command-line tools to display Node.js warnings by default instead of suppressing them.

[Copilot]

Copilot wasn't able to review any files in this pull request.

[coderabbitai]

Walkthrough

The shebang lines in the CLI scripts for two packages were updated by removing the --no-warnings flag from the Node.js invocation. This change means the scripts will now display Node.js warnings by default rather than suppressing them.

Changes

Files	Change Summary
packages/cli/bin/cli, packages/create-zenstack/bin/cli	Removed --no-warnings flag from Node.js shebang.

Poem

A bunny hopped to tweak the code,
No more warnings to forebode!
The flags are gone, the scripts now sing,
Let Node’s true messages take wing.
With every hop, a cleaner start—
🐇 Code and warnings, now apart!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a91f935 and ebd2bd7.

📒 Files selected for processing (2)

• packages/cli/bin/cli (1 hunks)
• packages/create-zenstack/bin/cli (1 hunks)

🔇 Additional comments (4)

packages/cli/bin/cli (2)

1-1: Portability improvement looks good.

Dropping the --no-warnings flag removes a POSIX-shebang portability foot-gun that breaks on some shells.
No other concerns for the line itself.

---

3-3: Double-check ESM pre-conditions for top-level import.

This file ends in .js, so Node will treat it as CommonJS unless the closest package.json contains "type": "module". Without that, the top-level import will throw a syntax error the moment the CLI executes.

Action:

1. Ensure packages/cli/package.json (or a parent) sets "type": "module".
2. Alternatively, rename the entry point to .mjs or switch to await import('../dist/index.js').

Please verify before publishing.

packages/create-zenstack/bin/cli (2)

1-1: Consistent shebang fix – looks good.

The same portability gain applies here; change is approved.

---

3-3: Ensure module type matches the top-level import.

Same concern as in packages/cli/bin/cli: the file relies on ESM semantics.

Confirm that packages/create-zenstack/package.json sets "type": "module" or switch to an .mjs filename/dynamic import.

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

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.

[ymc9]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.