build(deps-dev): bump the devdependencies group with 4 updates

[dependabot]

Bumps the devdependencies group with 4 updates: @astrojs/svelte, astro, cypress and tsx.

Updates @astrojs/svelte from 5.4.0 to 5.5.0

Release notes

Sourced from @​astrojs/svelte's releases.

@​astrojs/svelte@​5.5.0

Minor Changes

• #11144 803dd80 Thanks @​ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import ReactWrapper from '../src/components/ReactWrapper.astro';
  import { loadRenderers } from 'astro:container';
  import { getContainerRenderer } from '@astrojs/react';
  test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
  renderers,
  });
  const result = await container.renderToString(ReactWrapper);
  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
  });

Changelog

Sourced from @​astrojs/svelte's changelog.

5.5.0

Minor Changes

• #11144 803dd80 Thanks @​ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import ReactWrapper from '../src/components/ReactWrapper.astro';
  import { loadRenderers } from 'astro:container';
  import { getContainerRenderer } from '@astrojs/react';
  test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
  renderers,
  });
  const result = await container.renderToString(ReactWrapper);
  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
  });

Commits

• 48d5309 [ci] release (#11186)
• 803dd80 feat(container): provide a virtual module to load renderers (#11144)
• 464b0a1 fix(deps): update all non-major dependencies (#11151)
• f9b6f4f chore(deps): update all non-major dependencies (#10958)
• 05d58ef fix(deps): update all non-major dependencies (#10901)
• 8d5f3e8 chore(deps): update all non-major dependencies (#10833)
• See full diff in compare view

Updates astro from 4.9.2 to 4.10.1

Release notes

Sourced from astro's releases.

astro@4.10.1

Patch Changes

• #11198 8b9a499 Thanks @​florian-lefebvre! - Fixes a case where astro:env getSecret would not retrieve environment variables properly in dev and build modes

• #11206 734b98f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only

  Updates the adapter astro:env entrypoint from astro:env/setup to astro/env/setup

• #11205 8c45391 Thanks @​Nin3lee! - Fixes a typo in the config reference

astro@4.10.0

Minor Changes

• #10974 2668ef9 Thanks @​florian-lefebvre! - Adds experimental support for the astro:env API.

  The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

  ---
  import { PUBLIC_APP_ID } from 'astro:env/client';
  import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
  const API_TOKEN = getSecret('API_TOKEN');
  const data = await fetch(${PUBLIC_API_URL}/users, {
  method: 'POST',
  headers: {
  'Content-Type': 'application/json',
  Authorization: Bearer ${API_TOKEN},
  },
  body: JSON.stringify({ appId: PUBLIC_APP_ID }),
  });

  To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:

  // astro.config.mjs
  import { defineConfig, envField } from 'astro/config';
  export default defineConfig({
  experimental: {
  env: {
  schema: {
  PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
  PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
  API_SECRET: envField.string({ context: 'server', access: 'secret' }),
  },
  },

... (truncated)

Changelog

Sourced from astro's changelog.

4.10.1

Patch Changes

• #11198 8b9a499 Thanks @​florian-lefebvre! - Fixes a case where astro:env getSecret would not retrieve environment variables properly in dev and build modes

• #11206 734b98f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only

  Updates the adapter astro:env entrypoint from astro:env/setup to astro/env/setup

• #11205 8c45391 Thanks @​Nin3lee! - Fixes a typo in the config reference

4.10.0

Minor Changes

• #10974 2668ef9 Thanks @​florian-lefebvre! - Adds experimental support for the astro:env API.

  The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

  ---
  import { PUBLIC_APP_ID } from 'astro:env/client';
  import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
  const API_TOKEN = getSecret('API_TOKEN');
  const data = await fetch(${PUBLIC_API_URL}/users, {
  method: 'POST',
  headers: {
  'Content-Type': 'application/json',
  Authorization: Bearer ${API_TOKEN},
  },
  body: JSON.stringify({ appId: PUBLIC_APP_ID }),
  });

  To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:

  // astro.config.mjs
  import { defineConfig, envField } from 'astro/config';
  export default defineConfig({
  experimental: {
  env: {
  schema: {
  PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
  PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
  API_SECRET: envField.string({ context: 'server', access: 'secret' }),

... (truncated)

Commits

• 2da877b [ci] release (#11201)
• 734b98f feat(astro): update astro env setup (#11206)
• 8c45391 fix(astro:) config reference typo (#11205)
• 368e4ce [ci] format
• 8b9a499 fix(astro): getSecret in dev and build (#11198)
• 48d5309 [ci] release (#11186)
• 97fbe93 fix: merge userConfig inside getViteConfig (#11194)
• a64428d [ci] format
• 6e29a17 Make Astro.url in format: 'preserve' match dev (#11191)
• 58b10a0 Fix throw AstroUserError in mdx (#11192)
• Additional commits viewable in compare view

Updates cypress from 13.10.0 to 13.11.0

Release notes

Sourced from cypress's releases.

v13.11.0

Changelog: https://docs.cypress.io/guides/references/changelog#13-11-0

Commits

• 09c6876 chore: release 13.11.0 (#29615)
• e790891 feat: add option to ignore chrome preferences (#29447)
• 4ccdd86 misc: Add generic types to net-stubbing for use in intercept and wait (#29508)
• 687eb60 fix: Launchpad perpetual loading state, in certain circumstances (#29597)
• f2894c4 perf: optimize reduce in wrapConsoleProps (#29501)
• 41faa7e chore: Update Chrome (stable) to 125.0.6422.141 and Chrome (beta) to 126.0.64...
• ea83415 chore: move questions-remain into cypress repo (#29542)
• e6b422c chore: release @​cypress/webpack-dev-server-v3.9.0
• cf6b29d feat: support Next.JS version 14 (#29558)
• 2cf5cf8 chore(deps): Security upgrade micromatch from 4.0.4 to 4.0.6 (#29559)
• Additional commits viewable in compare view

Updates tsx from 4.11.2 to 4.15.1

Release notes

Sourced from tsx's releases.

v4.15.1

4.15.1 (2024-06-09)

Bug Fixes

• prevent ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE (fb247eb)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.15.0

4.15.0 (2024-06-09)

Features

• esbuild 0.21 (#19) (6f1d305)
• esbuild 0.21.3 (edbdfdf)
• esbuild 0.21.4 (c67d746)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.14.1

4.14.1 (2024-06-08)

Bug Fixes

• cjs: only hide transformers when namespaced (9e647a5)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.14.0

4.14.0 (2024-06-08)

... (truncated)

Commits

• fb247eb fix: prevent ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE
• c67d746 feat: esbuild 0.21.4
• edbdfdf feat: esbuild 0.21.3
• 6f1d305 feat: esbuild 0.21 (#19)
• bbbf1a7 refactor(cjs): organize resolver logic
• 9e647a5 fix(cjs): only hide transformers when namespaced
• 4503421 feat: resolve .js → .ts in package.json exports & main
• c35dbaa chore: add note about esm cjs interop optimization
• 807f467 fix(esm): cjs interop to support decorators
• 02d3856 fix(cjs): resolve directory import relative to parent (#42)
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[changeset-bot]

⚠️ No Changeset found

Latest commit: ad448e9

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]

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.

[sndrs]

@dependabot rebase

[sndrs]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[sndrs]

@dependabot recreate

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.