-
Notifications
You must be signed in to change notification settings - Fork 48
fix deploying Cloudflare:sockets and cloudflare email workers #723
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
base: main
Are you sure you want to change the base?
Conversation
|
@@ -104,7 +104,7 @@ export async function bundleServer(buildOpts: BuildOptions): Promise<void> { | |||
// Apply updater updates, must be the last plugin | |||
updater.plugin, | |||
] as Plugin[], | |||
external: ["./middleware/handler.mjs"], | |||
external: ["./middleware/handler.mjs", "cloudflare:sockets", "cloudflare:email"], |
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.
Thanks!
Would cloudflare:*
work here ?
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.
Yes, it should, also should it have node:*
?
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.
Yes, it should, also should it have
node:*
?
That is taken care of by platform: "node",
But we should have tests for cloudflare:*
:)
Thanks for the change, could you please add a patch changeset (using |
commit: |
Currently running issues, when running import 'cloudflare:email' in an API file Maybe I forgot server-only or could be related to the next config: |
Based on #661