Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency astro to v2.10.15 #24

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency astro to v2.10.15 #24

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
astro (source) 2.6.4 -> 2.10.15 age adoption passing 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:

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:

    // src/astro.config.mjs
export default defineConfig({
  output: 'server',
  adapter: node({
    mode: 'standalone',
  }),
  build: {
    split: true,
  },
});

  • #​7220 459b5bd05 Thanks @​ematipico! - The Astro hook astro:build:ssr now receives a new option in their payload, called entryPoints.

    entryPoints is defined as a Map<RouteData, URL>, where RouteData represents the information of a Astro route and URL is the path to the physical file emitted at the end of the build.

    export function integration(): AstroIntegration {
  return {
    name: 'my-integration',
    hooks: {
      'astro:build:ssr': ({ entryPoints }) => {
        // do something with `entryPoints`
      },
    },
  };
}
Patch Changes

  • #​7438 30bb36371 Thanks @​bluwy! - Fix astro:build:setup hook updateConfig utility, where the configuration wasn't correctly updated when the hook was fired.

  • #​7436 3943fa390 Thanks @​kossidts! - Fix an issue related to the documentation. Destructure the argument of the function to customize the Astro dev server based on the command run.

  • #​7424 7877a06d8 Thanks @​bholmesdev! - Update internal types for more stable builds for Astro maintainers.

  • #​7427 e314a04bf Thanks @​ematipico! - Correctly emit the middleware code during the build phase. The file emitted is now dist/middleware.mjs

  • #​7423 33cdc8622 Thanks @​bmenant! - Ensure injected /_image endpoint for image optimization is not prerendered on hybrid output.

v2.6.6

Compare Source

Patch Changes

v2.6.5

Compare Source

Patch Changes

Configuration

📅 Schedule: 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.

🔕 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.

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented May 1, 2024 •
edited
Loading

Important

Review skipped

Review was skipped due to path filters

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 7e99ab8 to 5936729 Compare June 27, 2024 13:53
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 5936729 to e7d8fc3 Compare August 31, 2024 15:08
@renovate renovate bot changed the title fix(deps): update dependency astro to v2.10.15 fix(deps): update dependency astro to v2.10.15 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/astro-monorepo branch December 8, 2024 18:39
@renovate renovate bot changed the title fix(deps): update dependency astro to v2.10.15 - autoclosed fix(deps): update dependency astro to v2.10.15 Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 4aea4a2 to e7d8fc3 Compare December 8, 2024 22:17
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
size/XXL
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants