-
Notifications
You must be signed in to change notification settings - Fork 830
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
Remove NodeJSCompatModule
#8666
Conversation
🦋 Changeset detectedLatest commit: 825a3af The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
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 |
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-wrangler-8666 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/8666/npm-package-wrangler-8666 Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-wrangler-8666 dev path/to/script.js Additional artifacts:cloudflare-workers-bindings-extension: wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-workers-bindings-extension-8666 -O ./cloudflare-workers-bindings-extension.0.0.0-v67b16d5af.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-v67b16d5af.vsix create-cloudflare: npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-create-cloudflare-8666 --no-auto-update @cloudflare/kv-asset-handler: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-kv-asset-handler-8666 miniflare: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-miniflare-8666 @cloudflare/pages-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-pages-shared-8666 @cloudflare/unenv-preset: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-unenv-preset-8666 @cloudflare/vite-plugin: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-vite-plugin-8666 @cloudflare/vitest-pool-workers: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-vitest-pool-workers-8666 @cloudflare/workers-editor-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-workers-editor-shared-8666 @cloudflare/workers-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-workers-shared-8666 @cloudflare/workflows-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/14104097440/npm-package-cloudflare-workflows-shared-8666 Note that these links will no longer work once the GitHub Actions artifact expires.
Please ensure constraints are pinned, and |
backport PR isn't created due to conflicts, so we'll need to create manually |
725737d
to
9a27f52
Compare
9a27f52
to
825a3af
Compare
if (mode !== "v2") { | ||
runnerWorker.compatibilityFlags.push("nodejs_compat_v2"); | ||
} |
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.
Could someone clarify this logic here? why are we adding the flag if not present?
(PS: I'm not saying that I think it's wrong, I'd just really like to understand this bit 🙂)
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.
maybe @petebacondarwin ? This code path is very unfamiliar to me. Worth noting tho that this PR doesn't change the logic by which these flags are applied, so if the original code was doing something wrong I would rather fix that in a followup PR, rather than block this PR on it?
Fixes n/a
This will soon be removed in
workerd
, and was never fully supported for deployed Workers. As such, it's being entirely removed.