search

guardian / csnx

Monorepo for Guardian UIs
https://guardian.github.io/csnx
Apache License 2.0
34 stars 2 forks source link

build(deps-dev): bump the devdependencies group across 1 directory with 3 updates #1595

Open dependabot[bot] opened 4 days ago

dependabot[bot] commented 4 days ago

Bumps the devdependencies group with 3 updates in the / directory: astro, @playwright/test and tsx.

Updates astro from 4.10.3 to 4.11.3

Release notes

Sourced from astro's releases.

astro@4.11.3

Patch Changes

  • #11347 33bdc54 Thanks @​bluwy! - Fixes installed packages detection when running astro check

  • #11327 0df8142 Thanks @​ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when using pnpm as package manager.

astro@4.11.2

Patch Changes

  • #11335 4c4741b Thanks @​ematipico! - Reverts #11292, which caused a regression to the input type

  • #11326 41121fb Thanks @​florian-lefebvre! - Fixes a case where running astro sync when using the experimental astro:env feature would fail if environment variables were missing

  • #11338 9752a0b Thanks @​zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent in rtl and ltr layouts

  • #11331 f1b78a4 Thanks @​bluwy! - Removes resolve package and simplify internal resolve check

  • #11339 8fdbf0e Thanks @​matthewp! - Remove non-fatal errors from telemetry

    Previously we tracked non-fatal errors in telemetry to get a good idea of the types of errors that occur in astro dev. However this has become noisy over time and results in a lot of data that isn't particularly useful. This removes those non-fatal errors from being tracked.

astro@4.11.1

Patch Changes

  • #11308 44c61dd Thanks @​ematipico! - Fixes an issue where custom 404.astro and 500.astro were not returning the correct status code when rendered inside a rewriting cycle.

  • #11302 0622567 Thanks @​martrapp! - Fixes an issue with the view transition router when redirecting to an URL with different origin.

  • Updated dependencies [b6afe6a, 41064ce]:

    • @​astrojs/markdown-remark@​5.1.1
    • @​astrojs/internal-helpers@​0.4.1

astro@4.11.0

Minor Changes

  • #11197 4b46bd9 Thanks @​braebo! - Adds ShikiTransformer support to the <Code /> component with a new transformers prop.

    Note that transformers only applies classes and you must provide your own CSS rules to target the elements of your code block.

    ---
import { transformerNotationFocus } from '@shikijs/transformers';
import { Code } from 'astro:components';

    const code = const foo = 'hello' const bar = ' world' console.log(foo + bar) // [!code focus] ;

... (truncated)

Changelog

Sourced from astro's changelog.

4.11.3

Patch Changes

  • #11347 33bdc54 Thanks @​bluwy! - Fixes installed packages detection when running astro check

  • #11327 0df8142 Thanks @​ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when using pnpm as package manager.

4.11.2

Patch Changes

  • #11335 4c4741b Thanks @​ematipico! - Reverts #11292, which caused a regression to the input type

  • #11326 41121fb Thanks @​florian-lefebvre! - Fixes a case where running astro sync when using the experimental astro:env feature would fail if environment variables were missing

  • #11338 9752a0b Thanks @​zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent in rtl and ltr layouts

  • #11331 f1b78a4 Thanks @​bluwy! - Removes resolve package and simplify internal resolve check

  • #11339 8fdbf0e Thanks @​matthewp! - Remove non-fatal errors from telemetry

    Previously we tracked non-fatal errors in telemetry to get a good idea of the types of errors that occur in astro dev. However this has become noisy over time and results in a lot of data that isn't particularly useful. This removes those non-fatal errors from being tracked.

4.11.1

Patch Changes

  • #11308 44c61dd Thanks @​ematipico! - Fixes an issue where custom 404.astro and 500.astro were not returning the correct status code when rendered inside a rewriting cycle.

  • #11302 0622567 Thanks @​martrapp! - Fixes an issue with the view transition router when redirecting to an URL with different origin.

  • Updated dependencies [b6afe6a, 41064ce]:

    • @​astrojs/markdown-remark@​5.1.1
    • @​astrojs/internal-helpers@​0.4.1

4.11.0

Minor Changes

  • #11197 4b46bd9 Thanks @​braebo! - Adds ShikiTransformer support to the <Code /> component with a new transformers prop.

    Note that transformers only applies classes and you must provide your own CSS rules to target the elements of your code block.

    ---
import { transformerNotationFocus } from '@shikijs/transformers';
import { Code } from 'astro:components';

    const code = `const foo = 'hello'

... (truncated)

Commits


Updates @playwright/test from 1.44.1 to 1.45.1

Release notes

Sourced from @​playwright/test's releases.

v1.45.1

Highlights

microsoft/playwright#31473 - [REGRESSION]: Playwright raises an error ENOENT: no such file or directory, open 'test-results/.playwright-artifacts-0/hash.zip' with Electron microsoft/playwright#31442 - [REGRESSION]: Locators of elements changing from/to hidden have operations hanging when using --disable-web-security microsoft/playwright#31431 - [REGRESSION]: NewTab doesn't work properly with Chrome with --disable-web-security microsoft/playwright#31425 - [REGRESSION]: beforeEach hooks are not skipped when describe condition depends on fixtures microsoft/playwright#31491 - [REGRESSION]: @playwright/experimental-ct-react doesn't work with VSCode extension and PNPM

Browser Versions

  • Chromium 127.0.6533.5
  • Mozilla Firefox 127.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 126
  • Microsoft Edge 126

v1.45.0

Clock

Utilizing the new Clock API allows to manipulate and control time within tests to verify time-related behavior. This API covers many common scenarios, including:

  • testing with predefined time;
  • keeping consistent time and timers;
  • monitoring inactivity;
  • ticking through time manually.
// Initialize clock and let the page load naturally.
await page.clock.install({ time: new Date('2024-02-02T08:00:00') });
await page.goto('http://localhost:3333');

// Pretend that the user closed the laptop lid and opened it again at 10am,
// Pause the time once reached that point.
await page.clock.pauseAt(new Date('2024-02-02T10:00:00'));


// Assert the page state.
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:00:00 AM');


// Close the laptop lid again and open it at 10:30am.
await page.clock.fastForward('30:00');
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:30:00 AM');

See the clock guide for more details.

Test runner

  • New CLI option --fail-on-flaky-tests that sets exit code to 1 upon any flaky tests. Note that by default, the test runner exits with code 0 when all failed tests recovered upon a retry. With this option, the test run will fail in such case.

... (truncated)

Commits


Updates tsx from 4.15.6 to 4.16.2

Release notes

Sourced from tsx's releases.

v4.16.2

4.16.2 (2024-07-03)

Bug Fixes

This release is also available on:

v4.16.1

4.16.1 (2024-07-03)

Bug Fixes

  • cjs: isolate implicit resolver enhancement (#59) (143a5bd)
  • cjs: namespace filter to preserve file path (6ef949c)
  • esm: implicit resolution with tsconfig paths (a74aa58), closes #607

This release is also available on:

v4.16.0

4.16.0 (2024-06-29)

Bug Fixes

  • cjs: tsx.require to support core modules (f748e19)

Features

  • cjs: improve compatibility with other loaders (3e1e546)

This release is also available on:

... (truncated)

Commits
  • 042be03 fix: isolated cts import in Node v18 (#61)
  • a74aa58 fix(esm): implicit resolution with tsconfig paths
  • 1603c66 refactor(cjs): cjs lexer detection
  • c6d5203 refactor(cjs): always inherit query from parent (#60)
  • aa3f2a1 test: scoped cts loading in Node v18
  • 8c61236 refactor(types): improve CJS module types
  • 23ebe7e refactor: preserve resolveFilename args accurately
  • e0b581c test: assert package can be loaded relative to data url
  • 143a5bd fix(cjs): isolate implicit resolver enhancement (#59)
  • 6ef949c fix(cjs): namespace filter to preserve file path
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
changeset-bot[bot] commented 4 days ago

⚠️ No Changeset found

Latest commit: c433c6b7af0a71ce0c213f5515f2547c6f78ecec

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.

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

github-actions[bot] commented 4 days ago

[!TIP] Once this PR is ready to go, add the run_chromatic label to run the Chromatic tests.

This saves us a lot of money by not running the tests before we need them.