-
Notifications
You must be signed in to change notification settings - Fork 782
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
Version Packages #8137
Version Packages #8137
Conversation
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/13327946933/npm-package-wrangler-8137 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/8137/npm-package-wrangler-8137 Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-wrangler-8137 dev path/to/script.js Additional artifacts:cloudflare-workers-bindings-extension: wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-workers-bindings-extension-8137 -O ./cloudflare-workers-bindings-extension.0.0.0-v304eefb00.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-v304eefb00.vsix create-cloudflare: npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-create-cloudflare-8137 --no-auto-update @cloudflare/kv-asset-handler: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-kv-asset-handler-8137 miniflare: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-miniflare-8137 @cloudflare/pages-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-pages-shared-8137 @cloudflare/unenv-preset: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-unenv-preset-8137 @cloudflare/vite-plugin: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-vite-plugin-8137 @cloudflare/vitest-pool-workers: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-vitest-pool-workers-8137 @cloudflare/workers-editor-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-workers-editor-shared-8137 @cloudflare/workers-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-workers-shared-8137 @cloudflare/workflows-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13327946933/npm-package-cloudflare-workflows-shared-8137 Note that these links will no longer work once the GitHub Actions artifact expires.
Please ensure constraints are pinned, and |
81e9393
to
a84df96
Compare
a84df96
to
cf0af2e
Compare
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@cloudflare/[email protected]
Patch Changes
#8118
ca3cbc4
Thanks @petebacondarwin! - fix Node.js compat module resolutionIn v0.0.8 we landed support for Vite 6.1 and also switched to using the new Cloudflare owned unenv preset.
Unfortunately, the changes made in that update caused a regression in Node.js support.
This became apparent only when the plugin was being used with certain package managers and outside of the workers-sdk monorepo.
The unenv polyfills that get compiled into the Worker are transitive dependencies of this plugin, not direct dependencies of the user's application were the plugin is being used.
This is on purpose to avoid the user having to install these dependencies themselves.
Unfortunately, the changes in 0.0.8 did not correctly resolve the polyfills from
@cloudflare/unenv-preset
andunenv
when the dependencies were not also installed directly into the user's application.The approach was incorrectly relying upon setting the
importer
in calls to Vite'sresolve(id, importer)
method to base the resolution in the context of the vite plugin package rather than the user's application.This doesn't work because the
importer
is only relevant when theid
is relative, and not a bare module specifier in the case of the unenv polyfills.This change fixes how these id are resolved in the plugin by manually resolving the path at the appropriate point, while still leveraging Vite's resolution pipeline to handle aliasing, and dependency optimization.
This change now introduces e2e tests that checks that isolated installations of the plugin works with npm, pnpm and yarn.
Updated dependencies [
28b1dc7
]:@cloudflare/[email protected]
Patch Changes
28b1dc7
]:[email protected]
Patch Changes
28b1dc7
Thanks @0xD34DC0DE! - fix: prevent __cf_cjs name collision in the hybrid Nodejs compat plugin