-
Notifications
You must be signed in to change notification settings - Fork 1k
Use more workerd native modules #11397
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
🦋 Changeset detectedLatest commit: e09e223 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the Depending on your changes, running Notes:
|
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
"BLOCKED, don't trust the CI" the tests are actually failing on CI because workerd is not updated in prod. But for some reason, the status is not reported correctly :( edit: addressed in #11399 |
32fddec to
37a8365
Compare
d8f69e8 to
8b868a3
Compare
8b868a3 to
7bbbcd4
Compare
7bbbcd4 to
e09e223
Compare
Node modules
punycode,trace_events,cluster,wasi, anddomainsare no more experimental since workerd 20251122.This PR uses workerd 20251125 as 202551122 and 202551123 have not been released to npm.
Note that remote tests are failing for now as 202551122 must not have been released to prod yet. A CI re-run should fix the error after the deployment.workerd was deployed/cc @anonrig @jasnell