search

yeskunall / www

🏞 My personal site built with Astro, Radix Colors, Tailwind, and deployed to Vercel
https://kimchiii.space
MIT License
2 stars 0 forks source link

build(deps): bump the astro group with 4 updates #248

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 2 weeks ago

Bumps the astro group with 4 updates: @astrojs/vercel, astro, @astrojs/mdx and @astrojs/sitemap.

Updates @astrojs/vercel from 7.6.0 to 7.7.1

Release notes

Sourced from @​astrojs/vercel's releases.

@​astrojs/vercel@​7.7.1

Patch Changes

@​astrojs/vercel@​7.7.0

Minor Changes

Changelog

Sourced from @​astrojs/vercel's changelog.

7.7.1

Patch Changes

7.7.0

Minor Changes

Commits


Updates astro from 4.8.6 to 4.11.0

Release notes

Sourced from astro's releases.

astro@4.11.0

Minor Changes

  • #11197 4b46bd9 Thanks @​braebo! - Adds ShikiTransformer support to the <Code /> component with a new transformers prop.

    Note that transformers only applies classes and you must provide your own CSS rules to target the elements of your code block.

    ---
import { transformerNotationFocus } from '@shikijs/transformers';
import { Code } from 'astro:components';

    const code = const foo = 'hello' const bar = ' world' console.log(foo + bar) // [!code focus] ;
    

    <Code {code} lang="js" transformers={[transformerNotationFocus()]} />
    

    <style is:global>
pre.has-focused .line:not(.focused) {
filter: blur(1px);
}
</style>

  • #11134 9042be0 Thanks @​florian-lefebvre! - Improves the developer experience of the 500.astro file by passing it a new error prop.

    When an error is thrown, the special src/pages/500.astro page now automatically receives the error as a prop. This allows you to display more specific information about the error on a custom 500 page.

    ---
// src/pages/500.astro
interface Props {
  error: unknown;
}

    const { error } = Astro.props;
    

    <div>{error instanceof Error ? error.message : 'Unknown error'}</div>

    If an error occurs rendering this page, your host's default 500 error page will be shown to your visitor in production, and Astro's default error overlay will be shown in development.

Patch Changes

... (truncated)

Changelog

Sourced from astro's changelog.

4.11.0

Minor Changes

  • #11197 4b46bd9 Thanks @​braebo! - Adds ShikiTransformer support to the <Code /> component with a new transformers prop.

    Note that transformers only applies classes and you must provide your own CSS rules to target the elements of your code block.

    ---
import { transformerNotationFocus } from '@shikijs/transformers';
import { Code } from 'astro:components';

    const code = const foo = 'hello' const bar = ' world' console.log(foo + bar) // [!code focus] ;
    

    <Code {code} lang="js" transformers={[transformerNotationFocus()]} />
    

    <style is:global>
pre.has-focused .line:not(.focused) {
filter: blur(1px);
}
</style>

  • #11134 9042be0 Thanks @​florian-lefebvre! - Improves the developer experience of the 500.astro file by passing it a new error prop.

    When an error is thrown, the special src/pages/500.astro page now automatically receives the error as a prop. This allows you to display more specific information about the error on a custom 500 page.

    ---
// src/pages/500.astro
interface Props {
  error: unknown;
}

    const { error } = Astro.props;
    

    <div>{error instanceof Error ? error.message : 'Unknown error'}</div>

    If an error occurs rendering this page, your host's default 500 error page will be shown to your visitor in production, and Astro's default error overlay will be shown in development.

Patch Changes

... (truncated)

Commits


Updates @astrojs/mdx from 3.0.0 to 3.1.1

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​3.1.1

Patch Changes

@​astrojs/mdx@​3.1.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({
renderers,
});
const result = await container.renderToString(ReactWrapper);
    

    expect(result).toContain('Counter');
expect(result).toContain('Count: <!-- -->5');
});

@​astrojs/mdx@​3.0.1

Patch Changes

  • #10813 3cc3e2c Thanks @​Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages
Changelog

Sourced from @​astrojs/mdx's changelog.

3.1.1

Patch Changes

3.1.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({
renderers,
});
const result = await container.renderToString(ReactWrapper);
    

    expect(result).toContain('Counter');
expect(result).toContain('Count: <!-- -->5');
});

3.0.1

Patch Changes

  • #10813 3cc3e2c Thanks @​Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages
Commits


Updates @astrojs/sitemap from 3.1.4 to 3.1.6

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.1.6

Patch Changes

@​astrojs/sitemap@​3.1.5

Patch Changes

Changelog

Sourced from @​astrojs/sitemap's changelog.

3.1.6

Patch Changes

3.1.5

Patch Changes

Commits


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 1 week ago

Looks like these dependencies are updatable in another way, so this is no longer needed.