Skip to content

Conversation

@penalosa
Copy link
Contributor

@penalosa penalosa commented Nov 6, 2025

A mix of outdated dependencies, fixing peer dependency warnings, running pnpm dedupe. See individual commits for details


  • Tests
    • Tests included
    • Tests not necessary because: existing tests should pass
  • Public documentation
    • Cloudflare docs PR(s):
    • Documentation not necessary because: internal refactor
  • Wrangler V3 Backport
    • Wrangler PR:
    • Not necessary because: refactor

…sed ws/MSW to drop the request host from the URL, breaking MSW
…ortunately cloudflare's types are pretty messy, so this is a bit of a messy change. However, in the spirit of dogfooding I think it's worth it—these warts will go away in time
…asset-handler tests. This package is no longer maintained or supported, and so I only made the minimal changes required to make it run, rather than the _actual_ right thing to do (migrate to vitest-pool-workers so that the tests run in a real environment
@penalosa penalosa requested review from a team as code owners November 6, 2025 19:10
@changeset-bot
Copy link

changeset-bot bot commented Nov 6, 2025

🦋 Changeset detected

Latest commit: fa078ee

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

@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 6, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11204

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11204

miniflare

npm i https://pkg.pr.new/miniflare@11204

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11204

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11204

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11204

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11204

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11204

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11204

wrangler

npm i https://pkg.pr.new/wrangler@11204

commit: fa078ee

@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2025

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main penalosa/update-deps might be a good starting point.

Notes:

  • your PR branch should be named v3-backport-11204
  • add the skip-v3-pr label to the current PR to stop this workflow from failing

}

await engineStub.receiveEvent({
const newStub = env.ENGINE.get(env.ENGINE.idFromName("MOCK-INSTANCE-ID"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to get a new stub for the same instance here?

"dependencies": {
"react": "^19.0.0",
"react-dom": "^19.0.0"
"react": "~19.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK so 19.2 is broken but most of these are currently on 19.1.xx.
Shouldn't these all be ~19.1.0 then?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw you fixed this in a later commit

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After further digging, it turned out to be 19.1.1 that's the first broken version

node_version: 22
# Browser rendering is disabled here because of https://pptr.dev/troubleshooting#issues-with-apparmor-on-ubuntu
filter: '--filter="./packages/*" --filter="./fixtures/*" --filter="./packages/vite-plugin-cloudflare/playground" --filter="!./packages/kv-asset-handler" --filter="!./fixtures/browser-rendering"'
filter: '--filter="./packages/*" --filter="./fixtures/*" --filter="./packages/vite-plugin-cloudflare/playground" --filter="!./fixtures/browser-rendering"'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kv-asset-handler no longer fails on node 22!

Comment on lines 92 to 147
test.skip("getAssetFromKV non ASCII path support", async (t) => {
mockRequestScope();
const event = getEvent(new Request("https://blah.com/测试.html"));
const res = await getAssetFromKV(event);

if (res) {
t.is(await res.text(), "My filename is non-ascii");
} else {
t.fail("Response was undefined");
}
});

test("getAssetFromKV supports browser percent encoded URLs", async (t) => {
mockRequestScope();
const event = getEvent(
new Request("https://example.com/%not-really-percent-encoded.html")
);
const res = await getAssetFromKV(event);

if (res) {
t.is(await res.text(), "browser percent encoded");
} else {
t.fail("Response was undefined");
}
});

test("getAssetFromKV supports user percent encoded URLs", async (t) => {
mockRequestScope();
const event = getEvent(new Request("https://blah.com/%2F.html"));
const res = await getAssetFromKV(event);

if (res) {
t.is(await res.text(), "user percent encoded");
} else {
t.fail("Response was undefined");
}
});

test("getAssetFromKV only decode URL when necessary", async (t) => {
mockRequestScope();
const event1 = getEvent(
new Request("https://blah.com/%E4%BD%A0%E5%A5%BD.html")
);
const event2 = getEvent(new Request("https://blah.com/你好.html"));
const res1 = await getAssetFromKV(event1);
const res2 = await getAssetFromKV(event2);

if (res1 && res2) {
t.is(await res1.text(), "Im important");
t.is(await res2.text(), "Im important");
} else {
t.fail("Response was undefined");
}
});

test("getAssetFromKV Support for user decode url path", async (t) => {
test.skip("getAssetFromKV Support for user decode url path", async (t) => {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These probably should be made to work, but the complexity of fixing them doesn't seem worth it, given we no longer support the package.

"dependencies": {
"react": "^19.0.0",
"react-dom": "^19.0.0"
"react": "~19.0.0",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After further digging, it turned out to be 19.1.1 that's the first broken version

@penalosa
Copy link
Contributor Author

penalosa commented Nov 7, 2025

This keeps going stale. I'm going to try and land the individual commits as individual PRs

@penalosa penalosa closed this Nov 7, 2025
@github-project-automation github-project-automation bot moved this from Untriaged to Done in workers-sdk Nov 7, 2025
@penalosa penalosa mentioned this pull request Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants