Bump astro from 4.9.3 to 4.10.0

[dependabot]

Bumps astro from 4.9.3 to 4.10.0.

Release notes

Sourced from astro's releases.

[email protected]

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' }),
  },
  },
  },
  });

  There are three kinds of environment variables, determined by the combination of context (client or server) and access (private or public) settings defined in your env.schema:

  • Public client variables: These variables end up in both your final client and server bundles, and can be accessed from both client and server through the astro:env/client module:

    import { PUBLIC_API_URL } from 'astro:env/client';

... (truncated)

Changelog

Sourced from astro's changelog.

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' }),
  },
  },
  },
  });

  There are three kinds of environment variables, determined by the combination of context (client or server) and access (private or public) settings defined in your env.schema:

  • Public client variables: These variables end up in both your final client and server bundles, and can be accessed from both client and server through the astro:env/client module:

    import { PUBLIC_API_URL } from 'astro:env/client';

... (truncated)

Commits

• 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)
• 4ad1ce2 [ci] format
• 1529428 [docs] format error messages (#11188)
• db71177 [ci] format
• 04b6421 [docs] formatting for astro:env (#11187)
• d03160a [ci] format
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
system-bridge-site-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 7, 2024 2:10am