Skip to content
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

chore(deps): update dependency miniflare to v3.20240610.1 #4

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 6, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
miniflare (source) 3.20240223.0 -> 3.20240610.1 age adoption passing confidence

Release Notes

cloudflare/workers-sdk (miniflare)

v3.20240610.1

Compare Source

Patch Changes
  • #​6050 a0c3327 Thanks @​threepointone! - chore: Normalize more deps

    This is the last of the patches that normalize dependencies across the codebase. In this batch: ws, vitest, zod , rimraf, @types/rimraf, ava, source-map, glob, cookie, @types/cookie, @microsoft/api-extractor, @types/mime, @types/yargs, devtools-protocol, @vitest/ui, execa, strip-ansi

    This patch also sorts dependencies in every package.json

  • #​6029 f5ad1d3 Thanks @​threepointone! - chore: Normalize some dependencies in workers-sdk

    This is the first of a few expected patches that normalize dependency versions, This normalizes undici, concurrently, @types/node, react, react-dom, @types/react, @types/react-dom, eslint, typescript. There are no functional code changes (but there are a couple of typecheck fixes).

  • #​6058 31cd51f Thanks @​threepointone! - chore: Quieter builds

    This patch cleans up warnings we were seeing when doing a full build. Specifically:

    • fixtures/remix-pages-app had a bunch of warnings about impending features that it should be upgraded to, so I did that. (tbh this one needs a full upgrade of packages, but we'll get to that later when we're upgrading across the codebase)
    • updated @microsoft/api-extractor so it didn't complain that it didn't match the typescript version (that we'd recently upgraded)
    • it also silenced a bunch of warnings when exporting types from wrangler. We'll need to fix those, but we'll do that when we work on unstable_dev etc.
    • workers-playground was complaining about the size of the bundle being generated, so I increased the limit on it

v3.20240610.0

Compare Source

Patch Changes
  • #​6024 c4146fc Thanks @​petebacondarwin! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20240605.0 1.20240610.1

v3.20240605.0

Compare Source

Patch Changes

v3.20240524.2

Compare Source

Patch Changes
  • #​5922 bdbb7f8 Thanks @​dario-piotrowicz! - fix: Allow the magic proxy to handle functions returning functions

    Previously functions returning functions would not be handled by the magic proxy,
    the changes here enable the above, allowing for code such as the following:

    	const mf = new Miniflare(/* ... */);
    
    	const { functionsFactory } = await mf.getBindings<Env>();
    	const fn = functionsFactory.getFunction();
    	const functionResult = fn();

    This also works with the native workers RPC mechanism, allowing users to
    return functions in their RPC code.

v3.20240524.1

Compare Source

Patch Changes

v3.20240524.0

Compare Source

Minor Changes
  • #​5917 64ccdd6 Thanks @​kossnocorp! - fix: D1's JOIN behaviour when selecting columns with the same name.

    Properly handle the resultsFormat query that workerd sends. This partially fixes the JOIN bug and makes the behaviour of raw consistent with the workerd behaviour.

Patch Changes

v3.20240512.0

Compare Source

Patch Changes

v3.20240419.1

Compare Source

Minor Changes
  • #​5570 66bdad0 Thanks @​sesteves! - feature: support delayed delivery in the miniflare's queue simulator.

    This change updates the miniflare's queue broker to support delayed delivery of messages, both when sending the message from a producer and when retrying the message from a consumer.

Patch Changes
  • #​5670 9b4af8a Thanks @​dario-piotrowicz! - fix: Allow the magic proxy to proxy objects containing functions

    This was previously prevented but this change removes that restriction.

v3.20240419.0

Compare Source

Patch Changes

v3.20240405.2

Compare Source

Patch Changes
  • #​5599 c9f081a Thanks @​penalosa! - fix: add support for wrapped bindings in magic proxy

    currently Miniflare#getBindings() does not return proxies to provided wrappedBindings, make sure that appropriate proxies are instead returned

    Example:

    import { Miniflare } from "miniflare";
    
    const mf = new Miniflare({
    	workers: [
    		{
    			wrappedBindings: {
    				Greeter: {
    					scriptName: "impl",
    				},
    			},
    			modules: true,
    			script: `export default { fetch(){ return new Response(''); } }`,
    		},
    		{
    			modules: true,
    			name: "impl",
    			script: `
    				class Greeter {
    					sayHello(name) {
    						return "Hello " + name;
    					}
    				}
    
    				export default function (env) {
    					return new Greeter();
    				}
    			`,
    		},
    	],
    });
    
    const { Greeter } = await mf.getBindings();
    
    console.log(Greeter.sayHello("world")); // <--- prints 'Hello world'
    
    await mf.dispose();
  • #​5599 c9f081a Thanks @​penalosa! - fix: add support for RPC in magic proxy

    currently Miniflare#getBindings() does not return valid proxies to provided serviceBindings using RPC, make sure that appropriate proxies are instead returned

    Example:

    import { Miniflare } from "miniflare";
    
    const mf = new Miniflare({
    	workers: [
    		{
    			modules: true,
    			script: `export default { fetch() { return new Response(''); } }`,
    			serviceBindings: {
    				SUM: {
    					name: "sum-worker",
    					entrypoint: "SumEntrypoint",
    				},
    			},
    		},
    		{
    			modules: true,
    			name: "sum-worker",
    			script: `
    				import { WorkerEntrypoint } from 'cloudflare:workers';
    
    				export default { fetch() { return new Response(''); } }
    
    				export class SumEntrypoint extends WorkerEntrypoint {
    					sum(args) {
    						return args.reduce((a, b) => a + b);
    					}
    				}
    			`,
    		},
    	],
    });
    
    const { SUM } = await mf.getBindings();
    
    const numbers = [1, 2, 3];
    
    console.log(`The sum of ${numbers.join(", ")} is ${await SUM.sum(numbers)}`); // <--- prints 'The sum of 1, 2, 3 is 6'
    
    await mf.dispose();

v3.20240405.1

Compare Source

Minor Changes
  • #​5409 08b4908 Thanks @​mrbbot! - feature: respect incoming Accept-Encoding header and ensure Accept-Encoding/request.cf.clientAcceptEncoding set correctly

    Previously, Miniflare would pass through the incoming Accept-Encoding header to your Worker code. This change ensures this header is always set to Accept-Encoding: br, gzip for incoming requests to your Worker. The original value of Accept-Encoding will be stored in request.cf.clientAcceptEncoding. This matches deployed behaviour.

    Fixes #​5246

v3.20240405.0

Compare Source

Patch Changes

v3.20240404.0

Compare Source

Patch Changes

v3.20240403.0

Compare Source

Minor Changes
  • #​5215 cd03d1d Thanks @​GregBrimble! - feature: customisable unsafe direct sockets entrypoints

    Previously, Miniflare provided experimental unsafeDirectHost and unsafeDirectPort options for starting an HTTP server that pointed directly to a specific Worker. This change replaces these options with a single unsafeDirectSockets option that accepts an array of socket objects of the form { host?: string, port?: number, entrypoint?: string, proxy?: boolean }. host defaults to 127.0.0.1, port defaults to 0, entrypoint defaults to default, and proxy defaults to false. This allows you to start HTTP servers for specific entrypoints of specific Workers. proxy controls the Style of the socket.

    Note these sockets set the capnpConnectHost workerd option to "miniflare-unsafe-internal-capnp-connect". external serviceBindings will set their capnpConnectHost option to the same value allowing RPC over multiple Miniflare instances. Refer to https://github.com/cloudflare/workerd/pull/1757 for more information.

  • #​5215 cd03d1d Thanks @​GregBrimble! - feature: support named entrypoints for serviceBindings

    This change allows service bindings to bind to a named export of another Worker using designators of the form { name: string | typeof kCurrentWorker, entrypoint?: string }. Previously, you could only bind to the default entrypoint. With this change, you can bind to any exported entrypoint.

    import { kCurrentWorker, Miniflare } from "miniflare";
    
    const mf = new Miniflare({
    	workers: [
    		{
    			name: "a",
    			serviceBindings: {
    				A_RPC_SERVICE: { name: kCurrentWorker, entrypoint: "RpcEntrypoint" },
    				A_NAMED_SERVICE: { name: "a", entrypoint: "namedEntrypoint" },
    				B_NAMED_SERVICE: { name: "b", entrypoint: "anotherNamedEntrypoint" },
    			},
    			compatibilityFlags: ["rpc"],
    			modules: true,
    			script: `
    			import { WorkerEntrypoint } from "cloudflare:workers";
    
    			export class RpcEntrypoint extends WorkerEntrypoint {
    				ping() { return "a:rpc:pong"; }
    			}
    
    			export const namedEntrypoint = {
    				fetch(request, env, ctx) { return new Response("a:named:pong"); }
    			};
    
    			...
    			`,
    		},
    		{
    			name: "b",
    			modules: true,
    			script: `
    			export const anotherNamedEntrypoint = {
    				fetch(request, env, ctx) { return new Response("b:named:pong"); }
    			};
    			`,
    		},
    	],
    });
Patch Changes
  • #​5499 6c3be5b Thanks @​GregBrimble! - chore: Bump workerd@1.20240403.0

  • #​5215 cd03d1d Thanks @​GregBrimble! - fix: allow scripts without scriptPaths to import built-in modules

    Previously, if a string script option was specified with modules: true but without a corresponding scriptPath, all imports were forbidden. This change relaxes that restriction to allow imports of built-in node:*, cloudflare:* and workerd:* modules without a scriptPath.

v3.20240329.1

Compare Source

Patch Changes
  • #​5491 940ad89 Thanks @​dario-piotrowicz! - fix: make sure the magic proxy can handle multiple parallel r2 stream reads

    Currently trying to read multiple R2 streams in parallel (via Promise.all for example) leads to deadlock which prevents any of the target streams from being read. This is caused by the underlying implementation only allowing a single HTTP connection to the Workers runtime at a time. This change fixes the issue by allowing multiple parallel HTTP connections.

v3.20240329.0

Compare Source

Minor Changes

v3.20240320.1

Compare Source

Minor Changes

v3.20240320.0

Compare Source

Patch Changes

v3.20240314.0

Compare Source

Minor Changes

v3.20240304.2

Compare Source

Patch Changes

v3.20240304.1

Compare Source

Patch Changes
  • #​5201 1235d48 Thanks @​wydengyre! - fix: ensure miniflare works with Node 21.7.0+

  • #​5191 27fb22b Thanks @​mrbbot! - fix: ensure redirect responses handled correctly with dispatchFetch()

    Previously, if your Worker returned a redirect response, calling dispatchFetch(url) would send another request to the original url rather than the redirect. This change ensures redirects are followed correctly.

    • If your Worker returns a relative redirect or an absolute redirect with the same origin as the original url, the request will be sent to the Worker.
    • If your Worker instead returns an absolute redirect with a different origin, the request will be sent to the Internet.
    • If a redirected request to a different origin returns an absolute redirect with the same origin as the original url, the request will also be sent to the Worker.

v3.20240304.0

Compare Source

Minor Changes

v3.20240223.1

Compare Source

Patch Changes
  • #​5133 42bcc72 Thanks @​mrbbot! - fix: ensure internals can access workerd when starting on non-local host

    Previously, if Miniflare was configured to start on a host that wasn't 127.0.0.1, ::1, *, ::, or 0.0.0.0, calls to Miniflare API methods relying on the magic proxy (e.g. getKVNamespace(), getWorker(), etc.) would fail. This change ensures workerd is always accessible to Miniflare's internals. This also fixes wrangler dev when using local network address such as 192.168.0.10 with the --ip flag.

  • #​5133 42bcc72 Thanks @​mrbbot! - fix: ensure IPv6 addresses can be used as hosts

    Previously, if Miniflare was configured to start on an IPv6 host, it could crash. This change ensures IPv6 addresses are handled correctly. This also fixes wrangler dev when using IPv6 addresses such as ::1 with the --ip flag.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

changeset-bot bot commented Mar 6, 2024

⚠️ No Changeset found

Latest commit: 0636d68

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240223.1 chore(deps): update dependency miniflare to v3.20240304.0 Mar 8, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240304.0 chore(deps): update dependency miniflare to v3.20240304.1 Mar 13, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240304.1 chore(deps): update dependency miniflare to v3.20240304.2 Mar 15, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240304.2 chore(deps): update dependency miniflare to v3.20240320.0 Mar 23, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240320.0 chore(deps): update dependency miniflare to v3.20240320.1 Mar 31, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240320.1 chore(deps): update dependency miniflare to v3.20240329.0 Apr 2, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240329.0 chore(deps): update dependency miniflare to v3.20240404.0 Apr 5, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240404.0 chore(deps): update dependency miniflare to v3.20240405.1 Apr 13, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240405.1 chore(deps): update dependency miniflare to v3.20240405.2 Apr 17, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240405.2 chore(deps): update dependency miniflare to v3.20240419.0 Apr 26, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240419.0 chore(deps): update dependency miniflare to v3.20240419.1 May 9, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240419.1 chore(deps): update dependency miniflare to v3.20240512.0 May 23, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240512.0 chore(deps): update dependency miniflare to v3.20240524.0 May 29, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240524.0 chore(deps): update dependency miniflare to v3.20240524.1 May 31, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240524.1 chore(deps): update dependency miniflare to v3.20240524.2 Jun 4, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240524.2 chore(deps): update dependency miniflare to v3.20240605.0 Jun 8, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240605.0 chore(deps): update dependency miniflare to v3.20240610.0 Jun 15, 2024
@renovate renovate bot changed the title chore(deps): update dependency miniflare to v3.20240610.0 chore(deps): update dependency miniflare to v3.20240610.1 Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants