Skip to content

fix(deps): update astro monorepo (major)#80

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo
Open

fix(deps): update astro monorepo (major)#80
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo

Conversation

@renovate

@renovate renovate Bot commented Dec 3, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/mdx (source) ^3.1.5 → ^7.0.0 age confidence
@astrojs/node (source) ^8.3.3 → ^11.0.0 age confidence
@astrojs/react (source) ^3.6.2 → ^6.0.0 age confidence
@astrojs/tailwind (source) ^5.1.0 → ^6.0.2 age confidence
astro (source) ^4.15.2 → ^7.0.3 age confidence

Release Notes

withastro/astro (@​astrojs/mdx)

v7.0.0

Compare Source

Major Changes
Minor Changes

  • #​17093 4585fe5 Thanks @​Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

    A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

    If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

    - import { getContainerRenderer } from '@​astrojs/react';
+ import { getContainerRenderer } from '@​astrojs/react/container-renderer';

    Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

  • #​17129 ff7b718 Thanks @​Princesseuh! - Adds support for modifying frontmatter programmatically with the default Markdown processor.

    A Sätteri plugin can now read and mutate ctx.data.astro.frontmatter, and Astro uses the result as the page's frontmatter, in both Markdown and MDX.

Patch Changes

v6.0.3

Compare Source

Patch Changes

  • #​16969 4a31f90 Thanks @​Princesseuh! - Adds support for Prism syntax highlighting to the Sätteri Markdown and MDX processors. Setting markdown.syntaxHighlight to 'prism' now highlights your code blocks with Prism.

    // astro.config.mjs
import { satteri } from '@​astrojs/markdown-satteri';

export default defineConfig({
  markdown: {
    processor: satteri(),
    syntaxHighlight: 'prism',
  },
});

v6.0.2

Patch Changes

v6.0.1

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​16848 f732f3c Thanks @​Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.

    Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.

    The default processor is unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { unified } from '@​astrojs/markdown-remark';
import remarkToc from 'remark-toc';

export default defineConfig({
  markdown: {
    processor: unified({
      remarkPlugins: [remarkToc],
    }),
  },
});

    In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing @astrojs/markdown-satteri, importing the satteri() processor, and adapting your existing configuration:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { satteri } from '@​astrojs/markdown-satteri';

export default defineConfig({
  markdown: {
    processor: satteri({
      features: { directive: true },
    }),
  },
});

    This processor does not support the remark and rehype plugins. This means you may need to convert them to MDAST or HAST plugins to retain your current functionality.

    The existing top-level markdown.remarkPlugins, markdown.rehypePlugins, markdown.remarkRehype, markdown.gfm, and markdown.smartypants options still work, but are now deprecated and will be removed in a future major update. The matching remarkPlugins, rehypePlugins, and remarkRehype options on the MDX integration are also deprecated for the same reason. To anticipate their removal, move them onto unified({...}) (or your preferred plugin processor) :

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import remarkToc from 'remark-toc';
import rehypeSlug from 'rehype-slug';
+ import { unified } from '@​astrojs/markdown-remark';

export default defineConfig({
  markdown: {
+    processor: unified({
+      remarkPlugins: [remarkToc],
+      rehypePlugins: [rehypeSlug],
+      remarkRehype: true,
+      gfm: true,
+      smartypants: true,
+    }),
-    remarkPlugins: [remarkToc],
-    rehypePlugins: [rehypeSlug],
-    remarkRehype: true,
-    gfm: true,
-    smartypants: true,
  },
});

    For more information on enabling and using this feature in your project, see our Markdown guide. To give feedback on this new Rust processor, see the Native Markdown / MDX parsing and processing RFC.

Minor Changes

  • #​16848 f732f3c Thanks @​Princesseuh! - Adds support for using @astrojs/markdown-satteri to parse .mdx files.

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import mdx from '@​astrojs/mdx';
import { satteri } from '@​astrojs/markdown-satteri';

export default defineConfig({
  markdown: {
    processor: satteri({
      features: { directive: true },
    }),
  },
  integrations: [mdx()],
});

    Note that the recmaPlugins option is not supported when using Sätteri as your MDX processor. If you would like to use Sätteri for Markdown files, but still use Unified for MDX, you can pass a different Markdown processor to the MDX integration:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import mdx from '@​astrojs/mdx';
import { satteri } from '@​astrojs/markdown-satteri';
import { unified } from '@​astrojs/markdown-remark';
import myPlugin from './my-recma-plugin.js';

export default defineConfig({
  markdown: {
    processor: satteri({
      features: { directive: true },
    }),
  },
  integrations: [
    mdx({
      recmaPlugins: [myPlugin],
      processor: unified(),
    }),
  ],
});
Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.3.14

Compare Source

Patch Changes

v4.3.13

Compare Source

Patch Changes

v4.3.12

Compare Source

Patch Changes

v4.3.11

Compare Source

Patch Changes

v4.3.10

Compare Source

Patch Changes

  • #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v4.3.9

Patch Changes

v4.3.8

Patch Changes

  • #​14591 3e887ec Thanks @​matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.

  • #​14598 7b45c65 Thanks @​delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

v4.3.7

Compare Source

Patch Changes

v4.3.6

Compare Source

Patch Changes

v4.3.5

Compare Source

Patch Changes

v4.3.4

Compare Source

Patch Changes

v4.3.3

Compare Source

Patch Changes

v4.3.2

Compare Source

Patch Changes

v4.3.1

Compare Source

Patch Changes

v4.3.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

v4.2.6

Compare Source

Patch Changes

v4.2.5

Compare Source

Patch Changes

v4.2.4

Compare Source

Patch Changes

v4.2.3

Compare Source

Patch Changes

v4.2.2

Patch Changes

v4.2.1

Patch Changes

v4.2.0

Compare Source

Minor Changes

  • #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

    By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
    special characters. This differs from the behavior of common Markdown processors.

    You can now disable this behavior with a new configuration flag:

    // astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    headingIdCompat: true,
  },
});

    This can be useful when heading IDs and anchor links need to behave consistently across your site
    and other platforms such as GitHub and npm.

    If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { rehypeHeadingIds } from '@​astrojs/markdown-remark';
import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';

export default defineConfig({
  markdown: {
    rehypePlugins: [
      [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
      otherPluginThatReliesOnHeadingIDs,
    ],
  },
});
Patch Changes

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes

  • #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

    Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

    Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

    No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

v4.0.8

Compare Source

Patch Changes

v4.0.7

Compare Source

Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

  • #​12921 aeb7e1a Thanks @​ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images

  • #​12913 9a3b48c Thanks @​bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

  • #​12231 90ae100 Thanks @​bluwy! - Handles the breaking change in Astro where content pages (including .mdx pages located within src/pages/) no longer respond with charset=utf-8 in the Content-Type header.

    For MDX pages without layouts, @astrojs/mdx will automatically add the <meta charset="utf-8"> tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the <meta charset="utf-8"> tag.

    If you require charset=utf-8 to render your page correctly, make sure that your layout components have the <meta charset="utf-8"> tag added.

  • #​12008 5608338 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

    Starting from this release, no breaking changes will be introduced unless absolutely necessary.

    To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

Minor Changes

  • #​12539 827093e Thanks @​bluwy! - Drops node 21 support

  • #​11741 6617491 Thanks @​bluwy! - Updates adapter server entrypoint to use @astrojs/mdx/server.js

    This is an internal change. Handling JSX in your .mdx files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.

Patch Changes

v3.1.9

Compare Source

Patch Changes

v3.1.8

Compare Source

Patch Changes

v3.1.7

Compare Source

Patch Changes

v3.1.6

Compare Source

Patch Changes
withastro/astro (@​astrojs/node)

v11.0.0

Compare Source

Patch Changes

v10.1.4

Compare Source

Patch Changes
  • #​16985 4ecff32 Thanks @​maximslo! - Fixes the experimental.logger destination not being used for the "Server listening on..." startup message. The logger is now resolved before the server starts listening, and adapterLogger re-creates itself when the underlying logger changes so the startup message uses the correct destination.

v10.1.3

Compare Source

Patch Changes

  • #​16922 7dce185 Thanks @​astrobot-houston! - Fixes prerendered pages returning 404 when using build.format: 'file' or build.format: 'preserve' with the Node adapter in standalone mode.

    Previously, clean URLs like /about would fail to resolve to about.html on disk, because the static file handler only supported the default directory format (about/index.html). Now the handler correctly resolves clean URLs to .html files when the build format produces them.

v10.1.2

Compare Source

Patch Changes

v10.1.1

Compare Source

Patch Changes

v10.1.0

Compare Source

Minor Changes

v10.0.6

Compare Source

Patch Changes

v10.0.5

Compare Source

Patch Changes
  • #​16319 940afd5 Thanks @​matthewp! - Fixes static asset error responses incorrectly including immutable cache headers. Conditional request failures (e.g. If-Match mismatch) now return the correct status code without far-future cache directives.

v10.0.4

Compare Source

Patch Changes

  • #​16002 846f27f Thanks @​buley! - Fixes file descriptor leaks from read streams that were not destroyed on client disconnect or read errors

  • #​15941 f41584a Thanks @​ematipico! - Fixes an infinite loop in resolveClientDir() when the server entry point is bundled with esbuild or similar tools. The function now throws a descriptive error instead of hanging indefinitely when the expected server directory segment is not found in the file path.

v10.0.3

Compare Source

Patch Changes

  • #​15735 9685e2d Thanks @​fa-sharp! - Fixes an EventEmitter memory leak when serving static pages from Node.js middleware.

    When using the middleware handler, requests that were being passed on to Express / Fastify (e.g. static files / pre-rendered pages / etc.) weren't cleaning up socket listeners before calling next(), causing a memory leak warning. This fix makes sure to run the cleanup before calling next().

v10.0.2

Compare Source

Patch Changes

v10.0.1

Compare Source

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the Dependencies label Dec 3, 2024
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 0c3f1bd to 28e8e9b Compare December 9, 2024 18:02
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from d821fb2 to 5a1251f Compare December 17, 2024 05:00
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 050533d to fc78783 Compare December 20, 2024 12:52
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 51c4189 to 0a233d9 Compare January 9, 2025 10:31
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from b05dca6 to 74bfbf8 Compare January 15, 2025 14:25
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from c00b9db to 679dee4 Compare January 27, 2025 13:25
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from c5648f4 to 5b7af22 Compare February 4, 2025 17:24
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from d1738e0 to 76b57eb Compare February 13, 2025 16:51
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 985747d to 29df1b5 Compare February 28, 2025 19:51
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 6 times, most recently from ae75030 to 825497f Compare April 18, 2025 15:27
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from f184300 to e15be30 Compare April 29, 2025 16:24
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 52e12b4 to 9d7c151 Compare May 6, 2025 19:57
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 1281369 to 4a5a3f4 Compare May 13, 2025 22:54
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 650bad6 to d6ccff5 Compare May 22, 2025 17:16
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 2560e86 to 5ec9ae6 Compare June 4, 2025 09:45
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 6e367b5 to ca907f4 Compare June 13, 2025 15:16
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 63ad03a to c2f4383 Compare June 23, 2025 13:47
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 48d0a9b to a526c6c Compare July 3, 2025 11:28
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from ac7f663 to 354de5a Compare July 16, 2025 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants