fix: replace invalid --env-file with dotenv-cli for tsup onSuccess

[Donal-Noye]

Description

Replaced --env-file flag (unsupported by Node.js) in the dev script of the live package with dotenv-cli. This prevents the CACError when starting the development server with yarn dev.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

No visual changes.

Test Scenarios

1. Run yarn dev inside the packages/live directory.
2. Confirm the server starts successfully and reads variables from .env.

References

None

Summary by CodeRabbit

• Chores
  • Updated the development and start scripts to improve environment variable loading.
  • Added a new dependency to support the updated environment loading process.

[coderabbitai]

Walkthrough

The dev and start scripts in the apps/live/package.json were updated to use dotenv-cli for environment variable loading instead of Node.js's native --env-file option. The dotenv-cli package was added as a dependency to support this change.

Changes

File(s)	Change Summary
apps/live/package.json	Updated dev and start scripts to use dotenv-cli for env loading; added dotenv-cli as a dependency.

Suggested reviewers

• lifeiscontent
• prateekshourya29
• vamsikrishnamathala

Poem

The script now runs with dotenv's might,
Loading secrets out of sight.
A tweak so small, yet so precise,
With dotenv-cli, things feel nice.
The rabbit hops with glee anew—
For every change brings something true! 🐇✨

---

📜 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 de69f01 and bb831a4.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• apps/live/package.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/live/package.json

---

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.

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.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between df4ea1f and de69f01.

📒 Files selected for processing (1)

• apps/live/package.json (2 hunks)

🔇 Additional comments (1)

apps/live/package.json (1)

59-60: dotenv-cli stays in devDependencies

The production start script uses Node’s native --env-file flag (not the dotenv binary), so only the dev script actually invokes dotenv-cli. Keeping it under devDependencies is correct.

• File: apps/live/package.json
• dev script: tsup --watch --onSuccess "dotenv -e .env -- node dist/server.js"
• start script: node --env-file=.env dist/server.js

No changes needed.

[sriramveeraghanta]

We are looking into implementing other alternatives like dotenvx than sticking to dotenv. Feel free to make those changes.