-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(cloudflare)!: Make the nodejs_compat entrypoint the default #22900
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Importing
vercelAIIntegrationfrom the main entrypoint will cause a startup crash in Cloudflare Workers environments that do not have thenodejs_compatflag enabled.Severity: HIGH
Suggested Fix
Revert the change that exports
vercelAIIntegrationfrom the main entrypoint (packages/cloudflare/src/index.ts). This integration and its Node.js-specific dependencies should be isolated in a separate entrypoint, such as the previously used@sentry/cloudflare/nodejs_compat, to prevent breaking users on runtimes without Node.js compatibility.Prompt for AI Agent
Also affects:
packages/cloudflare/src/index.ts:132Did we get this right? 👍 / 👎 to inform future reviews.