chore(deps): update all minor dependencies #46

renovate · 2024-12-30T20:07:25Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/js (source)	`9.17.0` -> `9.18.0`
@playwright/test (source)	`1.49.1` -> `1.50.0`
@schematics/angular	`~19.0.6` -> `~19.1.0`
@typescript-eslint/utils (source)	`8.18.2` -> `8.21.0`
eslint (source)	`9.17.0` -> `9.18.0`
jest-preset-angular (source)	`~14.4.2` -> `~14.5.0`
jest-preset-angular (source)	`~14.4.2` -> `~14.4.2 \|\| ~14.5.0`
ng-packagr	`~19.0.1` -> `~19.1.0`
postcss (source)	`8.4.49` -> `8.5.1`
typescript-eslint (source)	`8.18.2` -> `8.21.0`
wrangler (source)	`3.99.0` -> `3.105.0`

Release Notes

eslint/eslint (@eslint/js)

`v9.18.0`

Compare Source

microsoft/playwright (@playwright/test)

`v1.50.0`

Compare Source

Test runner

New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

New method test.step.skip() to disable execution of a test step.

test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.
Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.
Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.
New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.
```
npx playwright test --update-snapshots=changed --update-source-method=3way
```
Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.
Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.

UI updates

Updated default HTML reporter to improve display of attachments.
New button for picking elements to produce aria snapshots.
Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
Call and Network panels now display additional time information.

Breaking

expect(locator).toBeEditable() and locator.isEditable() now throw if the target element is not <input>, <select>, or a number of other editable elements.
Option testConfig.updateSnapshots now updates all snapshots when set to all, rather than only the failed/changed snapshots. Use the new enum changed to keep the old functionality of only updating the changed snapshots.

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

angular/angular-cli (@schematics/angular)

`v19.1.4`

Compare Source

`v19.1.3`

Compare Source

@angular/build

Commit	Type	Description
7d8c34172	fix	allow asset changes to reload page on incremental updates
9fa29af37	fix	handle relative `@ng/components`
c4de34703	fix	perform full reload for templates with `$localize` usage

`v19.1.2`

Compare Source

@angular/build

Commit	Type	Description
939d1612a	fix	perform incremental background file updates with component updates
304027207	fix	prevent full page reload on HMR updates with SSR enabled
148acbd58	fix	reset component updates on dev-server index request

`v19.1.1`

Compare Source

@angular/build

Commit	Type	Description
298506751	fix	resolve HMR-prefixed files in SSR with Vite

`v19.1.0`

Compare Source

Deprecations

@angular/build

The baseHref option under i18n.locales and i18n.sourceLocale in angular.json is deprecated in favor of subPath.

The subPath defines the URL segment for the locale, serving as both the HTML base HREF and the directory name for output. By default, if not specified, subPath will use the locale code.

@schematics/angular

Commit	Type	Description
02825eec5	feat	use `@angular/build` package in library generation schematic
88431b756	fix	application migration should migrate ng-packagr builder package

@angular-devkit/architect

Commit	Type	Description
2b8a02bac	feat	require build schemas from modules
fe1ae6933	fix	avoid Node.js resolution for relative builder schema

@angular-devkit/core

Commit	Type	Description
ce7c4e203	fix	handle Windows drive letter case insensitivity in path functions

@angular-devkit/schematics

Commit	Type	Description
2f55209dd	fix	update `Rule` type to support returning a `Promise` of `Tree`

@angular/build

Commit	Type	Description
2c9d7368f	feat	add ng-packagr builder to the package
0a570c0c2	feat	add support for customizing URL segments with i18n
298b554a7	feat	enable component template hot replacement by default
d350f357b	fix	correctly validate locales `subPath`
8aa1ce608	fix	handle loaders correctly in SSR bundles for external packages
3b7e6a8c6	fix	invalidate component template updates with dev-server SSR
8fa682e57	fix	remove deleted assets from output during watch mode
48cae815c	fix	skip vite SSR warmup file configuration when SSR is disabled
ba16ad6b5	fix	support incremental build file results in watch mode
955acef3d	fix	trigger browser reload on asset changes with Vite dev server
e74300a2c	fix	use component updates for component style HMR
6a19c217e	fix	warn when using both `isolatedModules` and `emitDecoratorMetadata`

@angular/ssr

Commit	Type	Description
8d7a51dfc	feat	add `modulepreload` for lazy-loaded routes
41ece633b	feat	redirect to preferred locale when accessing root route without a specified locale
3feecddbb	fix	disable component boostrapping when running route extraction
6edb90883	fix	throw error when using route matchers

`v19.0.7`

Compare Source

@angular-devkit/architect

Commit	Type	Description
95c22aeff	fix	provide better error when builder is not defined

@angular-devkit/build-angular

Commit	Type	Description
028652992	fix	preserve css type for jasmine.css

@angular/build

Commit	Type	Description
f7522342a	fix	add asset tracking to application builder watch files
e973643bf	fix	do not mark Babel _defineProperty helper function as pure
881095eec	fix	enable serving files with bundle-like names
db10af0b3	fix	fix incorrect budget calculation
c822f8f15	fix	handle relative URLs when constructing new URLs during server fetch
b43c648b0	fix	mitigate JS transformer worker execArgv errors
1f2481a4f	fix	pass `define` option defined in application builder to Vite prebundling
c94f568a4	fix	warn when `@angular/localize/init` is imported directly

typescript-eslint/typescript-eslint (@typescript-eslint/utils)

`v8.21.0`

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

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

`v8.20.0`

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

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

`v8.19.1`

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

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

`v8.19.0`

Compare Source

🩹 Fixes

eslint-plugin: [consistent-indexed-object-style] don't report on indirect circular references (#10537)

❤️ Thank You

Ronen Amiel

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

eslint/eslint (eslint)

`v9.18.0`

Compare Source

thymikee/jest-preset-angular (jest-preset-angular)

`v14.5.0`

Compare Source

Features

feat: add custom jsdom env #2904 (6045a96), closes #2883

Code Refactoring

refactor: add type for serializers/index.ts (dd64d78)

DEPRECATIONS

refactor: deprecate defaultTransformerOptions in presets (99d3112)
refactor: deprecate ngcc util via globalSetup (edeaa3f)

ng-packagr/ng-packagr (ng-packagr)

`v19.1.0`

Compare Source

Features

support TypeScript 5.7 (af70d03)

Bug Fixes

Re-use module resolution cache.
adjust peerDependencies to allow Angular 19.1.0-next (d27ef5b)

Performance

mitigate TypeScript 5.6+ performance regression (ac9766e), closes #2969

postcss/postcss (postcss)

`v8.5.1`

Compare Source

Fixed backwards compatibility for complex cases (by @romainmenke).

`v8.5.0`: 8.5 “Duke Alloces”

Compare Source

PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.

@romainmenke during his work on Stylelint added Input#document in additional to Input#css.

root.source.input.document //=> "<p>Hello</p>
                           //    <style>
                           //    p {
                           //      color: green;
                           //    }
                           //    </style>"
root.source.input.css      //=> "p {
                           //      color: green;
                           //    }"

Thanks to Sponsors

This release was possible thanks to our community.

If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:

Tidelift with a Spotify-like subscription model supporting all projects from your lock file.
Direct donations at GitHub Sponsors or Open Collective.

typescript-eslint/typescript-eslint (typescript-eslint)

`v8.21.0`

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

`v8.20.0`

Compare Source

🚀 Features

eslint-plugin: [no-misused-spread] add new rule (#10551)

❤️ Thank You

Josh Goldberg ✨

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

`v8.19.1`

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

`v8.19.0`

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

cloudflare/workers-sdk (wrangler)

`v3.105.0`

Compare Source

Minor Changes

#7466 e5ebdb1 Thanks @Ltadrian! - feat: implement the wrangler cert upload command

This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

For uploading mTLS certificate, run:
- wrangler cert upload mtls-certificate --cert cert.pem --key key.pem --name MY_CERT
For uploading CA certificate chain, run:
- wrangler cert upload certificate-authority --ca-cert server-ca.pem --name SERVER_CA

Patch Changes

#7867 bdc7958 Thanks @penalosa! - Revert https://github.com/cloudflare/workers-sdk/pull/7816. This feature added support for the ASSETS bindings to the getPlatformProxy() API, but caused a regression when running npm run preview in newly generated Workers Assets projects.
#7868 78a9a2d Thanks @penalosa! - Revert "Hyperdrive dev remote fix". This PR includes e2e tests that were not run before merging, and are currently failing.
Updated dependencies []:
- [email protected]

`v3.104.0`

Compare Source

Minor Changes

#7715 26fa9e8 Thanks @penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

#7816 f6cc029 Thanks @dario-piotrowicz! - add support for assets bindings to getPlatformProxy

this change makes sure that that getPlatformProxy, when the input configuration
file contains an assets field, correctly returns the appropriate asset binding proxy

example:

// wrangler.json
{
  "name": "my-worker",
  "assets": {
    "directory": "./public/",
    "binding": "ASSETS"
  },
  "vars": {
    "MY_VAR": "my-var"
  }
}

import { getPlatformProxy } from "wrangler";

const { env, dispose } = await getPlatformProxy();

if (env.ASSETS) {
  const text = await (
    await env.ASSETS.fetch("http://0.0.0.0/file.txt")
  ).text();
  console.log(text); // logs the content of file.txt
}

await dispose();

Patch Changes

#7785 cccfe51 Thanks @joshthoward! - Fix Durable Objects transfer migration validation
#7821 fcaa02c Thanks @vicb! - fix(wrangler): fix wrangler config schema defaults
#7832 97d2a1b Thanks @petebacondarwin! - Relax the messaging when Wrangler uses redirected configuration

Previously the messaging was rendered as a warning, which implied that the user
had done something wrong. Now it is just a regular info message.
#7806 d7adb50 Thanks @vicb! - chore: update unenv to 2.0.0-rc.0

Pull a couple changes in node:timers
- unjs/unenv#384 fix function bindings in node:timer
- unjs/unenv#385 implement active and _unrefActive in node:timer
The unenv update also includes #unjs/unenv/381 which implements
stdout, stderr and stdin of node:process with node:tty
#7828 9077a67 Thanks @edmundhung! - improve multi account error message in non-interactive mode
Updated dependencies []:
- [email protected]

`v3.103.2`

Compare Source

Patch Changes

#7804 16a9460 Thanks @vicb! - fix(wrangler): use require.resolve to resolve unenv path

`v3.103.1`

Compare Source

Patch Changes

#7798 a1ff045 Thanks @CarmenPopoviciu! - Reverts #7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)

`v3.103.0`

Compare Source

Minor Changes

#5086 8faf2c0 Thanks @dario-piotrowicz! - add --strict-vars option to wrangler types

add a new --strict-vars option to wrangler types that developers can (by setting the
flag to false) use to disable the default strict/literal types generation for their variables

opting out of strict variables can be useful when developers change often their vars values,
even more so when multiple environments are involved

`v3.102.0`

Compare Source

Minor Changes

#7592 f613276 Thanks @garrettgu10! - New filter validation logic supporting set and range queries in Vectorize CLI

Patch Changes

#7750 df0e5be Thanks @andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output of wrangler dev, and adds-in the same tag for Durable Objects (which are emulated locally in wrangler dev).
#7732 d102b60 Thanks @Ankcorn! - fix pages secret bulk copy
#7706 c63f1b0 Thanks @penalosa! - Remove the server-based dev registry in favour of the more stable file-based dev registry. There should be no user-facing impact.
Updated dependencies [8e9aa40]:
- [email protected]

`v3.101.0`

Compare Source

Minor Changes

#7534 7c8ae1c Thanks @cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines
#7674 45d1d1e Thanks @Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

Run wrangler secret bulk .dev.vars to add the env file
```
//.dev.vars
KEY=VALUE
KEY_2=VALUE
```
This will upload the secrets KEY and KEY_2 to your worker
#7442 e4716cc Thanks @petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

This new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
which Wrangler can use instead of user configuration when running deploy-related commands.
It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:

wrangler deploy
wrangler dev
wrangler versions upload
wrangler versions deploy
wrangler pages deploy
wrangler pages build
wrangler pages build-env

Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

{ "configPath": "../../path/to/wrangler.json" }

When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.

The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.
```
name = "my-worker"
main = "src/index.ts"
[[kv_namespaces]]
binding = "<BINDING_NAME1>"
id = "<NAMESPACE_ID1>"
```
Note that this configuration points main at user code entry-point.
The user runs a custom build, which might read the wrangler.toml to find the entry-point:
```
> my-tool build
```
This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:
```
- dist
  - index.js
	- wrangler.json
- .wrangler
  - deploy
	  - config.json
```
The dist/wrangler.json will contain:
```
{
  "name": "my-worker",
  "main": "./index.js",
  "kv_namespaces": [
    { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
  ]
}
```
And the .wrangler/deploy/config.json will contain:
```
{
  "configPath": "../../dist/wrangler.json"
}
```
#7685 9d2740a Thanks @vicb! - allow overriding the unenv preset.

By default wrangler uses the bundled unenv preset.

Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
Those paths are used when resolving the unenv module identifiers to absolute paths.
This can be used to test a development version.
#7694 f3c2f69 Thanks @joshthoward! - Default wrangler d1 export to --local rather than failing

Patch Changes

#7456 ff4e77e Thanks @andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.
#7712 6439347 Thanks @penalosa! - Remove CF-Connecting-IP for requests to the edge preview
#7703 e771fe9 Thanks @petebacondarwin! - include the top level Worker name in the parsed config structure
#7576 773bda8 Thanks @cmackenzie1! - Remove defaults for batch-max-* pipeline parameters and define value ranges
Updated dependencies [2c76887, 78bdec5]:
- [email protected]

`v3.100.0`

Compare Source

Minor Changes

#7604 6c2f173 Thanks @CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

#7581 cac7fa6 Thanks @vicb! - chore(wrangler): update unenv dependency version

unenv now uses the workerd implementation on node:dns
See the unjs/unenv#376
#7625 d8fb032 Thanks @vicb! - feat(wrangler): use unenv builtin dependency resolution

Moving away from require.resolve() to handle unenv aliased packages.
Using the unenv builtin resolution will allow us to drop the .cjs file from the preset
and to override the base path so that we can test the dev version of the preset.
#7533 755a27c Thanks @danielgek! - Add warning about the browser rendering not available on local
#7614 8abb43f Thanks @vicb! - chore(wrangler): update unenv dependency version

The updated unenv contains a fix for the module resolution,
see unjs/unenv#378.
That bug prevented us from using unenv module resolution,
see #7583.
Updated dependencies [b4e0af1]:
- [email protected]

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

github-actions · 2024-12-30T20:08:20Z