build(deps): bump the npm_and_yarn group across 1 directory with 2 updates

[dependabot]

Bumps the npm_and_yarn group with 2 updates in the / directory: @nuxtjs/mdc and esbuild.

Updates @nuxtjs/mdc from 0.16.1 to 0.17.0

Release notes

Sourced from @​nuxtjs/mdc's releases.

v0.17.0

🎉 Highlights

• Introduce MDCCached component, an efficient makdown parser and renderer for streaming texts.

[!NOTE] Markdown stringifier adds spaces around inline components. This is due to #371 fix.

🚀 Enhancements

• Introduce MDCCached component (#382)

🩹 Fixes

• Vue server renderer does not render \r causes hydration issue (b722c4a)
• Dynamic load parser in MDC component (#363)
• parser: Simplify filename regex in parseThematicBlock function (#367)
• MDCRenderer: Re-render when tags are modified (78a0571)
• stringify: Force hast-util-to-mdast to treat textComponent nodes as text (cd1c4fd)
• shiki: Allow overriding base transformers (760874d)
• md-highlighter: Import bundledLanguagesInfo directly from shiki (#375)
• Unify class properties (b820147)
• MDCRenderer: Ensure nodes are in right order on re-render (#381)
• Render button nodes (5242c08)
• stringify: Ensure inline components are separated by space (c9f538a)
• Do not add spacing around binding (c3efdd5)
• Do not add space between components and punctuation (6ea4163)
• Prevent undefined error (fc8c294)

💅 Refactors

• Imports for Shiki (#365)

📖 Documentation

• Fix link (bcb41b1)

🏡 Chore

• Upgrade deps (918ae96)
• Upgrade deps (418852c)
• Upgrade to latest remark-mdc (180983f)
• release: Release v0.17.0 (58e5ef0)

❤️ Contributors

• @​farnabaz
• @​productdevbook
• @​atinux

Changelog

Sourced from @​nuxtjs/mdc's changelog.

v0.17.0

compare changes

🚀 Enhancements

• Introduce MDCCached component (#382)

🩹 Fixes

• Vue server renderer does not render \r causes hydration issue (b722c4a)
• Dynamic load parser in MDC component (#363)
• parser: Simplify filename regex in parseThematicBlock function (#367)
• MDCRenderer: Re-render when tags are modified (78a0571)
• stringify: Force hast-util-to-mdast to treat textComponent nodes as text (cd1c4fd)
• shiki: Allow overriding base transformers (760874d)
• md-highlighter: Import bundledLanguagesInfo directly from shiki (#375)
• Unify class properties (b820147)
• MDCRenderer: Ensure nodes are in right order on re-render (#381)
• Render button nodes (5242c08)
• stringify: Ensure inline components are separated by space (c9f538a)
• Do not add spacing around binding (c3efdd5)
• Do not add space between components and punctuation (6ea4163)
• Prevent undefined error (fc8c294)

💅 Refactors

• Imports for Shiki (#365)

📖 Documentation

• Fix link (bcb41b1)

🏡 Chore

• Upgrade deps (918ae96)
• Upgrade deps (418852c)
• Upgrade to latest remark-mdc (180983f)

❤️ Contributors

• Farnabaz [email protected]
• Wind [email protected]
• Sébastien Chopin [email protected]
• Dev [email protected]

Commits

• 58e5ef0 chore(release): release v0.17.0
• 180983f chore: upgrade to latest remark-mdc
• fc8c294 fix: prevent undefined error
• 418852c chore: upgrade deps
• 6ea4163 fix: do not add space between components and punctuation
• c3efdd5 fix: do not add spacing around binding
• 4f74581 chore(deps): lock file maintenance (#374)
• c9f538a fix(stringify): ensure inline components are separated by space
• 5242c08 fix: render button nodes
• 918ae96 chore: upgrade deps
• Additional commits viewable in compare view

Updates esbuild from 0.25.2 to 0.25.4

Release notes

Sourced from esbuild's releases.

v0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com
    

  • JS:

    const ctx = await esbuild.context({})
    await ctx.serve({
      servedir: '.',
      cors: {
        origin: 'https://example.com',
      },
    })

  • Go:

    ctx, _ := api.Context(api.BuildOptions{})
    ctx.Serve(api.ServeOptions{
      Servedir: ".",
      CORS: api.CORSOptions{
        Origin: []string{"https://example.com"},
      },
    })

  The special origin * can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

• Pass through invalid URLs in source maps unmodified (#4169)

  This fixes a regression in version 0.25.0 where sources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation of sources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs in sources should now be passed through unmodified.

• Handle exports named __proto__ in ES modules (#4162, #4163)

  In JavaScript, the special property name __proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named __proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

  This fix was contributed by @​magic-akari.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com
    

  • JS:

    const ctx = await esbuild.context({})
    await ctx.serve({
      servedir: '.',
      cors: {
        origin: 'https://example.com',
      },
    })

  • Go:

    ctx, _ := api.Context(api.BuildOptions{})
    ctx.Serve(api.ServeOptions{
      Servedir: ".",
      CORS: api.CORSOptions{
        Origin: []string{"https://example.com"},
      },
    })

  The special origin * can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

• Pass through invalid URLs in source maps unmodified (#4169)

  This fixes a regression in version 0.25.0 where sources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation of sources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs in sources should now be passed through unmodified.

• Handle exports named __proto__ in ES modules (#4162, #4163)

  In JavaScript, the special property name __proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named __proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

... (truncated)

Commits

• 218d29e publish 0.25.4 to npm
• e66cd0b dev server: simple support for CORS requests (#4171)
• 8bf3368 js api: validate some options as arrays of strings
• 1e7375a js api: simplify comma-separated array validation
• 5f5964d release notes for #4163
• adb5284 fix: handle __proto__ as a computed property in exports and add tests for s...
• 0aa9f7b fix #4169: keep invalid source map URLs unmodified
• 5959289 add additional guards for #4114 when using :is()
• 677910b publish 0.25.3 to npm
• a41040e fix #4110: support custom non-IP host values
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.