Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented May 1, 2024

This PR contains the following updates:

Package Change Age Confidence
astro (source) 2.0.10 -> 2.10.15 age confidence

Release Notes

withastro/astro (astro)

v2.10.15

Compare Source

Patch Changes

v2.10.14

Compare Source

Patch Changes

v2.10.13

Compare Source

Patch Changes

v2.10.12

Compare Source

Patch Changes
  • #​8144 04caa99c4 Thanks @​lilnasy! - Fixed an issue where data entries' id included backslashes instead of forward slashes on Windows.

v2.10.11

Compare Source

Patch Changes

v2.10.10

Compare Source

Patch Changes
  • #​8127 b12c8471f Thanks @​natemoo-re! - Do not throw Error when users pass an object with a "type" property

  • #​8092 7177f7579 Thanks @​natemoo-re! - Ensure dotfiles are cleaned during static builds

  • #​8122 fa6b68a77 Thanks @​natemoo-re! - Improve fidelity of time stats when running astro build

  • #​8070 097a8e4e9 Thanks @​lilnasy! - Fix a handful of edge cases with prerendered 404/500 pages

  • #​8123 1f6497c33 Thanks @​natemoo-re! - Open to configured base when astro dev --open runs

  • #​8105 0e0fa605d Thanks @​martrapp! - ViewTransition: bug fix for lost scroll position in browser history

  • #​8116 b290f0a99 Thanks @​martrapp! - On back navigation only animate view transitions that were animated going forward.

  • #​7778 d6b494376 Thanks @​y-nk! - Added support for optimizing remote images from authorized sources when using astro:assets. This comes with two new parameters to specify which domains (image.domains) and host patterns (image.remotePatterns) are authorized for remote images.

    For example, the following configuration will only allow remote images from astro.build to be optimized:

    // astro.config.mjs
    export default defineConfig({
      image: {
        domains: ['astro.build'],
      },
    });

    The following configuration will only allow remote images from HTTPS hosts:

    // astro.config.mjs
    export default defineConfig({
      image: {
        remotePatterns: [{ protocol: 'https' }],
      },
    });
  • #​8109 da6e3da1c Thanks @​martrapp! - fix: reinsert attribute to specify direction of ViewTransition (forward / back)

v2.10.9

Compare Source

Patch Changes

v2.10.8

Compare Source

Patch Changes

v2.10.7

Compare Source

Patch Changes

v2.10.6

Compare Source

Patch Changes

v2.10.5

Compare Source

Patch Changes
  • #​8011 5b1e39ef6 Thanks @​bluwy! - Move hoisted script analysis optimization behind the experimental.optimizeHoistedScript option

v2.10.4

Compare Source

Patch Changes

v2.10.3

Compare Source

Patch Changes

v2.10.2

Compare Source

Patch Changes

v2.10.1

Compare Source

Patch Changes

v2.10.0

Compare Source

Minor Changes
  • #​7861 41afb8405 Thanks @​matthewp! - Persistent DOM and Islands in Experimental View Transitions

    With viewTransitions: true enabled in your Astro config's experimental section, pages using the <ViewTransition /> routing component can now access a new transition:persist directive.

    With this directive, you can keep the state of DOM elements and islands on the old page when transitioning to the new page.

    For example, to keep a video playing across page navigation, add transition:persist to the element:

    <video controls="" autoplay="" transition:persist>
      <source
        src="https://ia804502.us.archive.org/33/items/GoldenGa1939_3/GoldenGa1939_3_512kb.mp4"
        type="video/mp4"
      />
    </video>

    This <video> element, with its current state, will be moved over to the next page (if the video also exists on that page).

    Likewise, this feature works with any client-side framework component island. In this example, a counter's state is preserved and moved to the new page:

    <Counter count={5} client:load transition:persist />

    See our View Transitions Guide to learn more on usage.

Patch Changes

v2.9.7

Compare Source

Patch Changes

v2.9.6

Compare Source

Patch Changes

v2.9.5

Compare Source

Patch Changes

v2.9.4

Compare Source

Patch Changes

v2.9.3

Compare Source

Patch Changes
  • #​7782 0f677c009 Thanks @​bluwy! - Refactor Astro rendering to write results directly. This improves the rendering performance for all Astro files.

  • #​7786 188eeddd4 Thanks @​matthewp! - Execute scripts when navigating to a new page.

    When navigating to an new page with client-side navigation, scripts are executed (and re-executed) so that any new scripts on the incoming page are run and the DOM can be updated.

    However, type=module scripts never re-execute in Astro, and will not do so in client-side routing. To support cases where you want to modify the DOM, a new astro:load event listener been added:

    document.addEventListener('astro:load', () => {
      updateTheDOMSomehow();
    });

v2.9.2

Compare Source

Patch Changes

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

Minor Changes
  • #​7686 ec745d689 Thanks @​matthewp! - Redirects configuration

    This change moves the redirects configuration out of experimental. If you were previously using experimental redirects, remove the following experimental flag:

    experimental: {
      redirects: true,
    }

    If you have been waiting for stabilization before using redirects, now you can do so. Check out the docs on redirects to learn how to use this built-in feature.

  • #​7707 3a6e42e19 Thanks @​ottomated! - Improved hoisted script bundling

    Astro's static analysis to determine which <script> tags to bundle together just got a little smarter!

    Astro create bundles that optimize script usage between pages and place them in the head of the document so that they are downloaded as early as possible. One limitation to Astro's existing approach has been that you could not dynamically use hoisted scripts. Each page received the same, all-inclusive bundle whether or not every script was needed on that page.

    Now, Astro has improved the static analysis to take into account the actual imports used.

    For example, Astro would previously bundle the <script>s from both the <Tab> and <Accordian> component for the following library that re-exports multiple components:

    @​matthewp/my-astro-lib

    export { default as Tabs } from './Tabs.astro';
    export { default as Accordion } from './Accordion.astro';

    Now, when an Astro page only uses a single component, Astro will send only the necessary script to the page. A page that only imports the <Accordian> component will not receive any <Tab> component's scripts:

    ---
    import { Accordion } from '@&#8203;matthewp/my-astro-lib';
    ---

    You should now see more efficient performance with Astro now supporting this common library re-export pattern.

  • #​7511 6a12fcecb Thanks @​matthewp! - Built-in View Transitions Support (experimental)

    Astro now supports view transitions through the new <ViewTransitions /> component and the transition:animate (and associated) directives. View transitions are a great fit for content-oriented sites, and we see it as the best path to get the benefits of client-side routing (smoother transitions) without sacrificing the more simple mental model of MPAs.

    Enable support for view transitions in Astro 2.9 by adding the experimental flag to your config:

    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      experimental: {
        viewTransitions: true,
      },
    });

    This enables you to use the new APIs added.

This is a component which acts as the _router_ for transitions between pages. Add it to the `<head>` section of each individual page where transitions should occur _in the client_ as you navigate away to another page, instead of causing a full page browser refresh. To enable support throughout your entire app, add the component in some common layout or component that targets the `<head>` of every page.

**CommonHead.astro**

```astro
---
import { ViewTransitions } from 'astro:transitions';
---

<meta charset="utf-8" />
<title>{Astro.props.title}</title>
<ViewTransitions />
```

With only this change, your app will now route completely in-client. You can then add transitions to individual elements using the `transition:animate` directive.
Animations
Add `transition:animate` to any element to use Astro's built-in animations.

```astro
<header transition:animate="slide"></header>
```

In the above, Astro's `slide` animation will cause the `<header>` element to slide out to the left, and then slide in from the right when you navigate away from the page.

You can also customize these animations using any CSS animation properties, for example, by specifying a duration:

```astro
---
import { slide } from 'astro:transition';
---

<header transition:animate={slide({ duration: 200 })}></header>
```
Continue learning
Check out the [client-side routing docs](https://docs.astro.build/en/guides/client-side-routing/) to learn more.
Patch Changes

v2.8.5

Compare Source

Patch Changes

v2.8.4

Compare Source

Patch Changes

v2.8.3

Compare Source

Patch Changes

v2.8.2

Compare Source

Patch Changes

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Minor Changes
  • #​7532 9e5fafa2b Thanks @​ematipico! - The astro/middleware module exports a new utility called trySerializeLocals.

    This utility can be used by adapters to validate their locals before sending it
    to the Astro middleware.

    This function will throw a runtime error if the value passed is not serializable, so
    consumers will need to handle that error.

  • #​7532 9e5fafa2b Thanks @​ematipico! - Astro exposes the middleware file path to the integrations in the hook astro:build:ssr

    // myIntegration.js
    import type { AstroIntegration } from 'astro';
    function integration(): AstroIntegration {
      return {
        name: 'fancy-astro-integration',
        hooks: {
          'astro:build:ssr': ({ middlewareEntryPoint }) => {
            if (middlewareEntryPoint) {
              // do some operations
            }
          },
        },
      };
    }

    The middlewareEntryPoint is only defined if the user has created an Astro middleware.

  • #​7432 6e9c29579 Thanks @​ematipico! - Adds a new command astro info, useful for sharing debugging information about your current environment when you need help!

    astro info

    Output

    Astro version            v2.6.6
    Package manager          pnpm
    Platform                 darwin
    Architecture             arm64
    Adapter                  @&#8203;astrojs/vercel/serverless
    Integrations             None
    
  • #​7532 9e5fafa2b Thanks @​ematipico! - The astro/middleware module exports a new API called createContext.

    This a low-level API that adapters can use to create a context that can be consumed by middleware functions.

  • #​7532 9e5fafa2b Thanks @​ematipico! - Introduced a new build option for SSR, called build.excludeMiddleware.

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      build: {
        excludeMiddleware: true,
      },
    });

    When enabled, the code that belongs to be middleware won't be imported
    by the final pages/entry points. The user is responsible for importing it and
    calling it manually.

Patch Changes

v2.7.4

Compare Source

Patch Changes

v2.7.3

Compare Source

Patch Changes

v2.7.2

Compare Source

Patch Changes

v2.7.1

Compare Source

Patch Changes

v2.7.0

Compare Source

Minor Changes
  • #​7353 76fcdb84d Thanks @​bholmesdev! - Remove legacy handling for MDX content collections. Ensure you are using @astrojs/mdx v0.18 or above.

  • #​7385 8e2923cc6 Thanks @​ematipico! - Astro.locals is now exposed to the adapter API. Node Adapter can now pass in a locals object in the SSR handler middleware.

  • #​7220 459b5bd05 Thanks @​ematipico! - Shipped a new SSR build configuration mode: split.
    When enabled, Astro will "split" the single entry.mjs file and instead emit a separate file to render each individual page during the build process.

    These files will be emitted inside dist/pages, mirroring the directory structure of your page files in src/pages/, for example:

    ├── pages
    │   ├── blog
    │   │   ├── entry._slug_.astro.mjs
    │   │   └── entry.about.astro.mjs
    │   └── entry.index.astro.mjs
    

    To enable, set build.split: true in your Astro config:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from d2ea155 to a3e4b73 Compare January 30, 2025 16:19
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from a3e4b73 to 93ea0c8 Compare February 9, 2025 15:56
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 93ea0c8 to 37db3bd Compare March 3, 2025 13:43
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 35098f3 to f5c597d Compare March 17, 2025 13:55
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from f5c597d to 64f84f5 Compare April 1, 2025 08:52
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 64f84f5 to 4885ae0 Compare April 8, 2025 16:05
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 4885ae0 to b8592a8 Compare April 24, 2025 12:31
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from b8592a8 to 456429d Compare May 19, 2025 19:28
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 0a33580 to 7665777 Compare June 4, 2025 07:46
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 7665777 to e32b94f Compare June 22, 2025 11:08
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from e32b94f to e568a41 Compare July 2, 2025 20:27
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from b3dc017 to c3e2967 Compare August 13, 2025 13:33
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from c3e2967 to 21325a7 Compare August 19, 2025 11:48
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 21325a7 to 9feb213 Compare August 31, 2025 11:46
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 9feb213 to 20ffc9d Compare September 25, 2025 18:08
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 20ffc9d to 20d002a Compare October 21, 2025 19:00
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 20d002a to 2321047 Compare November 10, 2025 23:11
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 2321047 to 0ac2f5c Compare November 18, 2025 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant