Bump the npm_and_yarn group across 1 directory with 2 updates

[dependabot]

Bumps the npm_and_yarn group with 2 updates in the /docs directory: astro and tar-fs.

Updates astro from 5.13.2 to 5.14.4

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

• #14509 7e04caf Thanks @​ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

[email protected]

Patch Changes

• #14505 28b2a1d Thanks @​matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property

• #14235 c4d84bb Thanks @​toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

[email protected]

Patch Changes

• #14440 a3e16ab Thanks @​florian-lefebvre! - Fixes a case where the URLs generated by the experimental Fonts API would be incorrect in dev

[email protected]

Minor Changes

• #13520 a31edb8 Thanks @​openscript! - Adds a new property routePattern available to GetStaticPathsOptions

  This provides the original, dynamic segment definition in a routing file path (e.g. /[...locale]/[files]/[slug]) from the Astro render context that would not otherwise be available within the scope of getStaticPaths(). This can be useful to calculate the params and props for each page route.

  For example, you can now localize your route segments and return an array of static paths by passing routePattern to a custom getLocalizedData() helper function. The params object will be set with explicit values for each route segment (e.g. locale, files, and slug). Then, these values will be used to generate the routes and can be used in your page template via Astro.params.

  // src/pages/[...locale]/[files]/[slug].astro
  import { getLocalizedData } from "../../../utils/i18n"; export async function getStaticPaths({ routePattern
  }) { const response = await fetch('...'); const data = await response.json(); console.log(routePattern);
  // [...locale]/[files]/[slug] // Call your custom helper with routePattern to generate the static
  paths return data.flatMap((file) => getLocalizedData(file, routePattern)); } const { locale, files,
  slug } = Astro.params;

  For more information about this advanced routing pattern, see Astro's routing reference.

• #13651 dcfbd8c Thanks @​ADTC! - Adds a new SvgComponent type

  You can now more easily enforce type safety for your .svg assets by directly importing SVGComponent from astro/types:

  ---
  // src/components/Logo.astro
  import type { SvgComponent } from 'astro/types';
  import HomeIcon from './Home.svg';
  interface Link {
    url: string;
    text: string;

... (truncated)

Changelog

Sourced from astro's changelog.

5.14.4

Patch Changes

• #14509 7e04caf Thanks @​ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for the security.allowedDomains release.

5.14.3

Patch Changes

• #14505 28b2a1d Thanks @​matthewp! - Fixes Cannot set property manifest error in test utilities by adding a protected setter for the manifest property

• #14235 c4d84bb Thanks @​toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabled

5.14.2

Patch Changes

• #14459 916f9c2 Thanks @​florian-lefebvre! - Improves font files URLs in development when using the experimental fonts API by showing the subset if present

• b8ca69b Thanks @​ascorbic! - Aligns dev image server file base with Vite rules

• #14469 1c090b0 Thanks @​delucis! - Updates tinyexec dependency

• #14460 008dc75 Thanks @​florian-lefebvre! - Fixes a case where astro:config/server values typed as URLs would be serialized as strings

• #13730 7260367 Thanks @​razonyang! - Fixes a bug in i18n, where Astro caused an infinite loop when a locale that doesn't have an index, and Astro falls back to the index of the default locale.

• 6ee63bf Thanks @​matthewp! - Adds security.allowedDomains configuration to validate X-Forwarded-Host headers in SSR

  The X-Forwarded-Host header will now only be trusted if it matches one of the configured allowed host patterns. This prevents host header injection attacks that can lead to cache poisoning and other security vulnerabilities.

  Configure allowed host patterns to enable X-Forwarded-Host support:

  // astro.config.mjs
  export default defineConfig({
    output: 'server',
    adapter: node(),
    security: {
      allowedDomains: [
        { hostname: 'example.com' },
        { hostname: '*.example.com' },
        { hostname: 'cdn.example.com', port: '443' },
      ],
    },
  });

  The patterns support wildcards (* and **) for flexible hostname matching and can optionally specify protocol and port.

... (truncated)

Commits

• 3412859 [ci] release (#14510)
• 7e04caf docs: fix security.allowedDomains version (#14509)
• fe1d35c [ci] release (#14507)
• 7926882 [ci] format
• c4d84bb fix(prefetch): Fix "tap" prefetch strategy when view transitions are enabled ...
• 3bb14b7 [ci] release (#14466)
• 7a5aaff [ci] format
• 28b2a1d Fix failing x-forwarded-host tests (#14505)
• ec307b0 [ci] format
• 6ee63bf Merge commit from fork
• Additional commits viewable in compare view

Updates tar-fs from 2.1.3 to 2.1.4

Commits

• f421a23 2.1.4
• c412fa1 refactor to same pattern as v3
• See full diff in compare view

Updates tar-fs from 3.0.9 to 3.1.1

Commits

• f421a23 2.1.4
• c412fa1 refactor to same pattern as v3
• 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
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[Adam-it]

I checked this change locally and it seems that when running our docs locally no images load on the page

this is something that does not happen when running docs from main branch

[Adam-it]

before we proceed we need to understand what is breaking the images.
Also I want to check it with some npm package security scanners, although I tried package-security-checker and it seems none of the packages we use are on the corrupted npm packages list

[Adam-it]

I figured it out and it seems in the updated astro package the behavior changed.
now astro only supports rendering images that are part of the public images or/and assets folder which are in the docs folder. Images outside of the docs folder are not being served. This means we have a problem as we reuse many images from the extension assets folder

[Adam-it]

I figured it out and it seems in the updated astro package the behavior changed. now astro only supports rendering images that are part of the public images or/and assets folder which are in the docs folder. Images outside of the docs folder are not being served. This means we have a problem as we reuse many images from the extension assets folder

The idea is to move our VS Code images to docs folder and in the vscode-ignore file exclude everything except the new images folder

[Adam-it]

this will be done in #631

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml