build(deps): bump the minor-and-patch group across 1 directory with 8 updates

[dependabot]

Bumps the minor-and-patch group with 8 updates in the /site directory:

Package	From	To
@astrojs/check	0.6.0	0.9.1
@astrojs/solid-js	4.2.0	4.4.0
astro	4.8.3	4.13.0
solid-js	1.8.17	1.8.19
three	0.164.1	0.167.1
@types/three	0.164.0	0.167.1
typescript	5.4.5	5.5.4
@playwright/test	1.44.0	1.45.3

Updates @astrojs/check from 0.6.0 to 0.9.1

Release notes

Sourced from @​astrojs/check's releases.

@​astrojs/check@​0.9.1

Patch Changes

• cc94bef: Revert a change to top-level returns that could prevent the return types of functions from being correct in certain cases
• Updated dependencies [cc94bef]
  • @​astrojs/language-server@​2.13.1

@​astrojs/check@​0.9.0

Minor Changes

• b65d6b4: Adds support for SCSS and LESS intellisense inside style tags

Patch Changes

• Updated dependencies [3a60f00]
• Updated dependencies [b65d6b4]
  • @​astrojs/language-server@​2.13.0

@​astrojs/check@​0.8.3

Patch Changes

• 0a46801: Fixes a regression where errors could wrongly show (or not show) inside scripts and style tags
• Updated dependencies [0a46801]
• Updated dependencies [72f61e1]
  • @​astrojs/language-server@​2.12.7

@​astrojs/check@​0.8.2

Patch Changes

• 708167e: Fixes script and style tags being wrongfully included in the generated TSX
• Updated dependencies [708167e]
  • @​astrojs/language-server@​2.12.1

@​astrojs/check@​0.8.1

Patch Changes

• 5eb20f2: Fixes installation on Yarn 4
• Updated dependencies [5eb20f2]
  • @​astrojs/language-server@​2.11.1

@​astrojs/check@​0.8.0

Minor Changes

• b8a6af3: Upgrades to the latest version of Volar, the underlying framework powering the Astro language server. This update should fix some of the recent issues regarding intellisense inside script tags.

Patch Changes

• a1769da: Adds a README with helpful links
• Updated dependencies [b8a6af3]
  • @​astrojs/language-server@​2.11.0

... (truncated)

Changelog

Sourced from @​astrojs/check's changelog.

0.9.1

Patch Changes

• cc94bef: Revert a change to top-level returns that could prevent the return types of functions from being correct in certain cases
• Updated dependencies [cc94bef]
  • @​astrojs/language-server@​2.13.1

0.9.0

Minor Changes

• b65d6b4: Adds support for SCSS and LESS intellisense inside style tags

Patch Changes

• Updated dependencies [3a60f00]
• Updated dependencies [b65d6b4]
  • @​astrojs/language-server@​2.13.0

0.8.3

Patch Changes

• 0a46801: Fixes a regression where errors could wrongly show (or not show) inside scripts and style tags
• Updated dependencies [0a46801]
• Updated dependencies [72f61e1]
  • @​astrojs/language-server@​2.12.7

0.8.2

Patch Changes

• 708167e: Fixes script and style tags being wrongfully included in the generated TSX
• Updated dependencies [708167e]
  • @​astrojs/language-server@​2.12.1

0.8.1

Patch Changes

• 5eb20f2: Fixes installation on Yarn 4
• Updated dependencies [5eb20f2]
  • @​astrojs/language-server@​2.11.1

0.8.0

Minor Changes

• b8a6af3: Upgrades to the latest version of Volar, the underlying framework powering the Astro language server. This update should fix some of the recent issues regarding intellisense inside script tags.

... (truncated)

Commits

• 492b2bf Version Packages (#926)
• 93b5c30 Version Packages (#925)
• 97d2558 Version Packages (#917)
• 48689d1 Version Packages (#906)
• 4a10d24 Version Packages (#899)
• 9e45765 Version Packages (#894)
• b8a6af3 feat: Update to Volar 2.4 alpha (#879)
• a1769da Add @astrojs/check README (#883)
• 260167f Version Packages (#873)
• See full diff in compare view

Updates @astrojs/solid-js from 4.2.0 to 4.4.0

Release notes

Sourced from @​astrojs/solid-js's releases.

@​astrojs/solid-js@​4.4.0

Minor Changes

• #11234 4385bf7 Thanks @​ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

  This new function should be preferred when using the Container API in environments like on-demand pages:

  import type { APIRoute } from 'astro';
  import { experimental_AstroContainer } from 'astro/container';
  import reactRenderer from '@astrojs/react/server.js';
  import vueRenderer from '@astrojs/vue/server.js';
  import ReactComponent from '../components/button.jsx';
  import VueComponent from '../components/button.vue';
  // MDX runtime is contained inside the Astro core
  import mdxRenderer from 'astro/jsx/server.js';
  // In case you need to import a custom renderer
  import customRenderer from '../renderers/customRenderer.js';
  export const GET: APIRoute = async (ctx) => {
  const container = await experimental_AstroContainer.create();
  container.addServerRenderer({ renderer: reactRenderer });
  container.addServerRenderer({ renderer: vueRenderer });
  container.addServerRenderer({ renderer: customRenderer });
  // You can pass a custom name too
  container.addServerRenderer({
  name: 'customRenderer',
  renderer: customRenderer,
  });
  const vueComponent = await container.renderToString(VueComponent);
  return await container.renderToResponse(Component);
  };

@​astrojs/solid-js@​4.3.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({

... (truncated)

Changelog

Sourced from @​astrojs/solid-js's changelog.

4.4.0

Minor Changes

• #11234 4385bf7 Thanks @​ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

  This new function should be preferred when using the Container API in environments like on-demand pages:

  import type { APIRoute } from 'astro';
  import { experimental_AstroContainer } from 'astro/container';
  import reactRenderer from '@astrojs/react/server.js';
  import vueRenderer from '@astrojs/vue/server.js';
  import ReactComponent from '../components/button.jsx';
  import VueComponent from '../components/button.vue';
  // MDX runtime is contained inside the Astro core
  import mdxRenderer from 'astro/jsx/server.js';
  // In case you need to import a custom renderer
  import customRenderer from '../renderers/customRenderer.js';
  export const GET: APIRoute = async (ctx) => {
  const container = await experimental_AstroContainer.create();
  container.addServerRenderer({ renderer: reactRenderer });
  container.addServerRenderer({ renderer: vueRenderer });
  container.addServerRenderer({ renderer: customRenderer });
  // You can pass a custom name too
  container.addServerRenderer({
  name: 'customRenderer',
  renderer: customRenderer,
  });
  const vueComponent = await container.renderToString(VueComponent);
  return await container.renderToResponse(Component);
  };

4.3.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 () => {

... (truncated)

Commits

• 83c565b [ci] release (#11233)
• 68f1d0d chore(deps): update all non-major dependencies (#11269)
• d4336a5 [ci] format
• fd9da98 feat: refine container APIs for renderers (#11251)
• 8725cb2 fix(deps): update all non-major dependencies (#11222)
• 48d5309 [ci] release (#11186)
• 803dd80 feat(container): provide a virtual module to load renderers (#11144)
• 464b0a1 fix(deps): update all non-major dependencies (#11151)
• See full diff in compare view

Updates astro from 4.8.3 to 4.13.0

Release notes

Sourced from astro's releases.

[email protected]

Minor Changes

• #11507 a62345f Thanks @​ematipico! - Adds color-coding to the console output during the build to highlight slow pages.

  Pages that take more than 500 milliseconds to render will have their build time logged in red. This change can help you discover pages of your site that are not performant and may need attention.

• #11379 e5e2d3e Thanks @​alexanderniebuhr! - The experimental.contentCollectionJsonSchema feature introduced behind a flag in v4.5.0 is no longer experimental and is available for general use.

  If you are working with collections of type data, Astro will now auto-generate JSON schema files for your editor to get IntelliSense and type-checking. A separate file will be created for each data collection in your project based on your collections defined in src/content/config.ts using a library called zod-to-json-schema.

  This feature requires you to manually set your schema's file path as the value for $schema in each data entry file of the collection:

  {
    "$schema": "../../../.astro/collections/authors.schema.json",
    "name": "Armand",
    "skills": ["Astro", "Starlight"]
  }

  Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's json.schemas setting, provide the path of files to match and the location of your JSON schema:

  {
    "json.schemas": [
      {
        "fileMatch": ["/src/content/authors/**"],
        "url": "./.astro/collections/authors.schema.json"
      }
    ]
  }

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  export default defineConfig({
  
  experimental: {
  contentCollectionJsonSchema: true
  }
  })

If you have been waiting for stabilization before using JSON Schema generation for content collections, you can now do so.

Please see the content collections guide for more about this feature.

... (truncated)

Changelog

Sourced from astro's changelog.

4.13.0

Minor Changes

• #11507 a62345f Thanks @​ematipico! - Adds color-coding to the console output during the build to highlight slow pages.

  Pages that take more than 500 milliseconds to render will have their build time logged in red. This change can help you discover pages of your site that are not performant and may need attention.

• #11379 e5e2d3e Thanks @​alexanderniebuhr! - The experimental.contentCollectionJsonSchema feature introduced behind a flag in v4.5.0 is no longer experimental and is available for general use.

  If you are working with collections of type data, Astro will now auto-generate JSON schema files for your editor to get IntelliSense and type-checking. A separate file will be created for each data collection in your project based on your collections defined in src/content/config.ts using a library called zod-to-json-schema.

  This feature requires you to manually set your schema's file path as the value for $schema in each data entry file of the collection:

  {
    "$schema": "../../../.astro/collections/authors.schema.json",
    "name": "Armand",
    "skills": ["Astro", "Starlight"]
  }

  Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's json.schemas setting, provide the path of files to match and the location of your JSON schema:

  {
    "json.schemas": [
      {
        "fileMatch": ["/src/content/authors/**"],
        "url": "./.astro/collections/authors.schema.json"
      }
    ]
  }

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  export default defineConfig({
  
  experimental: {
  contentCollectionJsonSchema: true
  }
  })

If you have been waiting for stabilization before using JSON Schema generation for content collections, you can now do so.

Please see the content collections guide for more about this feature.

... (truncated)

Commits

• 4474887 [ci] release (#11578)
• 6aaeec5 Update errors-data.ts for Astro.rewrite release in 4.13 (#11580)
• 750d532 fix(deps): update all non-major dependencies (#11565)
• 45ad326 feat: stabilise the rewrite APIs (#11542)
• a62345f feat: log slow pages in red (#11507)
• 2cf770d [ci] format
• e5e2d3e chore: unflag contentCollectionJsonSchema (#11379)
• 60b2766 Verify you can use server:defer on self-imported module (#11577)
• 49db004 [ci] release (#11524)
• 9f766d8 [ci] format
• Additional commits viewable in compare view

Updates solid-js from 1.8.17 to 1.8.19

Commits

• See full diff in compare view

Updates three from 0.164.1 to 0.167.1

Commits

• See full diff in compare view

Updates @types/three from 0.164.0 to 0.167.1

Commits

• See full diff in compare view

Updates typescript from 5.4.5 to 5.5.4

Release notes

Sourced from typescript's releases.

TypeScript 5.5.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.4 (Stable).
• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package (soon!)

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.5.0 (Beta).

... (truncated)

Commits

• c8a7d58 Bump version to 5.5.4 and LKG
• c0ded04 🤖 Pick PR #58771 (Allow references to the global Symb...) into release-5.5 (#...
• 5ba41e2 🤖 Pick PR #59208 (Write non-missing undefined on mapp...) into release-5.5 (#...
• b075332 🤖 Pick PR #59337 (Allow declarationMap to be emitted ...) into release-5.5 (#...
• 9dd6f91 Cherry-pick "Stop using latest Node in CI" to release-5.5 (#59348)
• bf0ddaf 🤖 Pick PR #59070 (Delay the calculation of common sou...) into release-5.5 (#...
• a44e2d9 🤖 Pick PR #59160 (Fixed crash on authored import type...) into release-5.5 (#...
• f35206d 🤖 Pick PR #59325 (Don't skip markLinkedReferences on ...) into release-5.5 (#...
• 1109550 Fix baselines on release-5.5 (#59330)
• 8794318 🤖 Pick PR #59215 (Fix codefix crash on circular alias...) into release-5.5 (#...
• Additional commits viewable in compare view

Updates @playwright/test from 1.44.0 to 1.45.3

Release notes

Sourced from @​playwright/test's releases.

v1.45.3

Highlights

microsoft/playwright#31764 - [Bug]: some actions do not appear in the trace file microsoft/playwright-java#1617 - [Bug]: Traceviewer not reporting all actions

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.2

Highlights

microsoft/playwright#31613 - [REGRESSION]: Trace is not showing any screenshots nor test name microsoft/playwright#31601 - [REGRESSION]: missing trace for 2nd browser microsoft/playwright#31541 - [REGRESSION]: Failing tests have a trace with no images and with steps missing

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.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

... (truncated)

Commits

• 0e130fa chore: mark v1.45.3 (#31799)
• 2f17a27 cherry-pick(#31781): chore: show error when opening newer trace with … (#31797)
• b129aba cherry-pick(#31768): fix(trace viewer): library-only trace should not merge a...
• d8a5f3b chore: mark v1.45.2 (#31702)
• 51fa0ff Revert "chore: move artifacts recording to TestLifecycleInstrumentation (#309...
• 80f44f3 cherry-pick(#31666): Revert "fix(chromium): pass --enable-gpu when running he...
• 4bd2d25 cherry-pick(#31511): docs(clock): update time types in Python/.NET
• e8989f8 chore: mark v1.45.1 (#31516)
• 1d94caa cherry-pick(#31496): docs(release-notes): fix .NET snippets
• 5be5168 cherry-pick(#31504): fix(ct): export package.json
• 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