chore(deps): bump the dependencies group in /website with 2 updates

[dependabot]

Bumps the dependencies group in /website with 2 updates: @astrojs/starlight and astro.

Updates @astrojs/starlight from 0.35.0 to 0.35.1

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.35.1

Patch Changes

• #3325 4cf28f2 Thanks @​mniinio! - Adds Finnish language support

Changelog

Sourced from @​astrojs/starlight's changelog.

0.35.1

Patch Changes

• #3325 4cf28f2 Thanks @​mniinio! - Adds Finnish language support

Commits

• bec2c47 [ci] release (#3326)
• 4cf28f2 Support for Finnish language (fi) (#3325)
• See full diff in compare view

Updates astro from 5.11.2 to 5.12.0

Release notes

Sourced from astro's releases.

[email protected]

Minor Changes

• #13971 fe35ee2 Thanks @​adamhl8! - Adds an experimental flag rawEnvValues to disable coercion of import.meta.env values (e.g. converting strings to other data types) that are populated from process.env

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type.

  However, Astro also converts your environment variables used through import.meta.env in some cases, and this can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.rawEnvValues flag disables coercion of import.meta.env values that are populated from process.env, allowing you to use the raw value.

  To enable this feature, add the experimental flag in your Astro config:

  import { defineConfig } from "astro/config"
  export default defineConfig({
  
  experimental: {
  rawEnvValues: true,
  }
  })

If you were relying on this coercion, you may need to update your project code to apply it manually:

- const enabled: boolean = import.meta.env.ENABLED
+ const enabled: boolean = import.meta.env.ENABLED === "true"

See the experimental raw environment variables reference docs for more information.

#13941 6bd5f75 Thanks @​aditsachde! - Adds support for TOML files to Astro's built-in glob() and file() content loaders.

In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader.

Astro 5.12 now directly supports loading data from TOML files in content collections in both the glob() and the file() loaders.

If you had added your own TOML content parser for the file() loader, you can now remove it as this functionality is now included:

// src/content.config.ts
import { defineCollection } from "astro:content";
import { file } from "astro/loaders";
- import { parse as parseToml } from "toml";
const dogs = defineCollection({
-  loader: file("src/data/dogs.toml", { parser: (text) => parseToml(text) }),
+ loader: file("src/data/dogs.toml")
  schema: /* ... */
})

... (truncated)

Changelog

Sourced from astro's changelog.

5.12.0

Minor Changes

• #13971 fe35ee2 Thanks @​adamhl8! - Adds an experimental flag rawEnvValues to disable coercion of import.meta.env values (e.g. converting strings to other data types) that are populated from process.env

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type.

  However, Astro also converts your environment variables used through import.meta.env in some cases, and this can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.rawEnvValues flag disables coercion of import.meta.env values that are populated from process.env, allowing you to use the raw value.

  To enable this feature, add the experimental flag in your Astro config:

  import { defineConfig } from "astro/config"
  export default defineConfig({
  
  experimental: {
  rawEnvValues: true,
  }
  })

If you were relying on this coercion, you may need to update your project code to apply it manually:

- const enabled: boolean = import.meta.env.ENABLED
+ const enabled: boolean = import.meta.env.ENABLED === "true"

See the experimental raw environment variables reference docs for more information.

#13941 6bd5f75 Thanks @​aditsachde! - Adds support for TOML files to Astro's built-in glob() and file() content loaders.

In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader.

Astro 5.12 now directly supports loading data from TOML files in content collections in both the glob() and the file() loaders.

If you had added your own TOML content parser for the file() loader, you can now remove it as this functionality is now included:

// src/content.config.ts
import { defineCollection } from "astro:content";
import { file } from "astro/loaders";
- import { parse as parseToml } from "toml";
const dogs = defineCollection({
-  loader: file("src/data/dogs.toml", { parser: (text) => parseToml(text) }),
+ loader: file("src/data/dogs.toml")
  schema: /* ... */

... (truncated)

Commits

• ca05a2f [ci] release (#14084)
• d2305bc fix punctuation in an error message (#14085)
• 6bd5f75 feat: Add TOML support to the built-in content loaders (#13941)
• fe35ee2 don't coerce environment variable values when populating import.meta.env (#13...
• See full diff 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

[cloudflare-workers-and-pages]

Deploying htmlhint with    Cloudflare Pages

Latest commit:	0c54a35
Status:	✅  Deploy successful!
Preview URL:	https://7b968ea9.htmlhint.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-webs-oori.htmlhint.pages.dev

View logs