-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: npm run dev #3446
fix: npm run dev #3446
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
related: https://linear.app/eliza-labs/issue/ELI2-16/fix-npm-run-dev
I noticed two issues with npm run dev:
Bun blocking untrusted packages – Bun blocks certain packages at postinstall, requiring users to run bun i twice for npm run dev to work. This PR adds trustedDependencies to ensure all necessary packages install correctly on the first run.
Inconsistent build order – The current setup causes build errors due to an inconsistent execution order. This PR use a script to enforce the correct build sequence before running dev.
Test steps:
bun i
npm run dev