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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update npm development dependencies #10827

Merged
merged 2 commits into from
Apr 8, 2024
Merged

chore(deps): update npm development dependencies #10827

merged 2 commits into from
Apr 8, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 8, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types 4.20240329.0 -> 4.20240405.0 age adoption passing confidence
@types/react (source) 18.2.73 -> 18.2.74 age adoption passing confidence
@types/react-dom (source) 18.2.23 -> 18.2.24 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 7.4.0 -> 7.5.0 age adoption passing confidence
@typescript-eslint/parser (source) 7.4.0 -> 7.5.0 age adoption passing confidence
eslint (source) ^8.30.0 -> ^9.0.0 age adoption passing confidence
miniflare (source) 3.20240329.0 -> 3.20240404.0 age adoption passing confidence
typescript (source) 5.4.3 -> 5.4.4 age adoption passing confidence
vite (source) 5.2.7 -> 5.2.8 age adoption passing confidence
wrangler (source) 3.42.0 -> 3.48.0 age adoption passing confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20240405.0

Compare Source

v4.20240404.0

Compare Source

v4.20240403.0

Compare Source

v4.20240402.0

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.5.0

Compare Source

🩹 Fixes

  • eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression

  • eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option

❤️ Thank You
  • Brad Zacher
  • Kim Sang Du
  • Mark de Dios
  • Naru
  • YeonJuan

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.5.0

Compare Source

🩹 Fixes
  • parser: disallow errorOnTypeScriptSyntacticAndSemanticIssues
❤️ Thank You
  • Brad Zacher
  • Kim Sang Du
  • Mark de Dios
  • Naru
  • YeonJuan

You can read about our versioning strategy and releases on our website.

eslint/eslint (eslint)

v9.0.0

Compare Source

cloudflare/workers-sdk (miniflare)

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 [email protected]

  • #​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.

Microsoft/TypeScript (typescript)

v5.4.4: TypeScript 5.4.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

vitejs/vite (vite)

v5.2.8

Compare Source

cloudflare/workers-sdk (wrangler)

v3.48.0

Compare Source

Minor Changes

  • #​5429 c5561b7 Thanks @​ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it is
    enabled on your account.

    Wrangler supports an -s flag that allows the user to specify a storage class when creating a bucket,
    changing the default storage class of a bucket, and uploading an object.

    wrangler r2 bucket create ia-bucket -s InfrequentAccess
wrangler r2 bucket update storage-class my-bucket -s InfrequentAccess
wrangler r2 object put bucket/ia-object -s InfrequentAccess --file foo
Patch Changes

v3.47.1

Compare Source

Patch Changes

v3.47.0

Compare Source

Minor Changes
  • #​5506 7734f80 Thanks @​penalosa! - feat: Add interactive prompt to wrangler pages download config if an existing wrangler.toml file exists

v3.46.0

Compare Source

Minor Changes

  • #​5282 b7ddde1 Thanks @​maxwellpeterson! - feature: Add source map support for Workers

    Adds the source_maps boolean config option. When enabled, source maps included in the build output are uploaded alongside the built code modules. Uploaded source maps can then be used to remap stack traces emitted by the Workers runtime.

  • #​5215 cd03d1d Thanks @​GregBrimble! - feature: support named entrypoints in service bindings

    This change allows service bindings to bind to a named export of another Worker. As an example, consider the following Worker named bound:

    import { WorkerEntrypoint } from "cloudflare:workers";

export class EntrypointA extends WorkerEntrypoint {
	fetch(request) {
		return new Response("Hello from entrypoint A!");
	}
}

export const entrypointB: ExportedHandler = {
	fetch(request, env, ctx) {
		return new Response("Hello from entrypoint B!");
	}
};

export default <ExportedHandler>{
	fetch(request, env, ctx) {
		return new Response("Hello from the default entrypoint!");
	}
};

    Up until now, you could only bind to the default entrypoint. With this change, you can bind to EntrypointA or entrypointB too using the new entrypoint option:

    [[services]]
binding = "SERVICE"
service = "bound"
entrypoint = "EntrypointA"

    To bind to named entrypoints with wrangler pages dev, use the # character:

    $ wrangler pages dev --service=SERVICE=bound#EntrypointA
Patch Changes

  • #​5215 cd03d1d Thanks @​GregBrimble! - fix: ensure request url and cf properties preserved across service bindings

    Previously, Wrangler could rewrite url and cf properties when sending requests via service bindings or Durable Object stubs. To match production behaviour, this change ensures these properties are preserved.

  • Updated dependencies [cd03d1d, 6c3be5b, cd03d1d, cd03d1d]:

v3.45.0

Compare Source

Minor Changes

  • #​5377 5d68744 Thanks @​CarmenPopoviciu! - feat: Add wrangler.toml support in wrangler pages deploy

    As we are adding wrangler.toml support for Pages, we want to ensure that wrangler pages deploy works with a configuration file.

  • #​5471 489b9c5 Thanks @​zebp! - feature: Add version-id filter for Worker tailing to filter logs by scriptVersion in a gradual deployment

    This allows users to only get logs in a gradual deployment if you are troubleshooting issues
    specific to one deployment. Example:
    npx wrangler tail --version-id 72d3f357-4e52-47c5-8805-90be978c403f

Patch Changes

v3.44.0

Compare Source

Minor Changes

  • #​5461 f69e562 Thanks @​mattdeboard! - feature: Add command for fetching R2 Event Notification configurations for a given bucket

    This allows users to see the entire event notification configuration -- i.e. every rule for every configured queue -- for a single bucket with a single request.

    This change also improves messaging of console output when creating a new bucket notification.

Patch Changes

v3.43.0

Compare Source

Minor Changes
Patch Changes

Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

@renovate renovate bot added the internal An internal refactor or improvement label Apr 8, 2024
@MichaReiser MichaReiser enabled auto-merge (squash) April 8, 2024 06:52
@MichaReiser
Copy link
Member

I tested the different development workflows and played with npm run preview

@MichaReiser MichaReiser merged commit 86419c8 into main Apr 8, 2024
17 checks passed
@MichaReiser MichaReiser deleted the renovate/npm-development-dependencies branch April 8, 2024 07:00
@charliermarsh charliermarsh mentioned this pull request Apr 11, 2024
Merged
dhruvmanila pushed a commit that referenced this pull request Apr 11, 2024
@charliermarsh
Downgrade ESLint to v8 (#10888)
9b9098c 
## Summary

Some of our plugins aren't compatible with v9.

Originally shipped in #10827.

## Test Plan

- `npm install`
- `npm ci`
Glyphack pushed a commit to Glyphack/ruff that referenced this pull request Apr 12, 2024
@renovate @MichaReiser @Glyphack
chore(deps): update npm development dependencies (astral-sh#10827)
177771a 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Micha Reiser <[email protected]>
Glyphack pushed a commit to Glyphack/ruff that referenced this pull request Apr 12, 2024
@charliermarsh @Glyphack
Downgrade ESLint to v8 (astral-sh#10888)
1c35879 
## Summary

Some of our plugins aren't compatible with v9.

Originally shipped in astral-sh#10827.

## Test Plan

- `npm install`
- `npm ci`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MichaReiser MichaReiser MichaReiser approved these changes

Assignees
No one assigned
Labels
internal An internal refactor or improvement
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@MichaReiser