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

Update dependency astro to ^0.26.0 #17

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

Update dependency astro to ^0.26.0 #17

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 1, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
astro (source) ^0.21.4 -> ^0.26.0 age adoption passing confidence

Release Notes

withastro/astro (astro)

v0.26.1

Compare Source

v0.26.0: Astro v0.26.0

Compare Source

Migration Guide & What's New: https://docs.astro.build/en/migrate/#migrate-to-v026
Full Changelog: https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#0260

v0.25.4

Compare Source

Patch Changes

v0.25.3

Compare Source

Patch Changes

v0.25.2

Compare Source

Patch Changes

v0.25.1

Compare Source

Patch Changes

v0.25.0

Upgrading from v0.24 or earlier? Check out the Migration Guide.

Breaking & Minor Changes

  • #​2820 Thanks @​FredKSchott! - New Astro Integrations System!
    Full Documentation

  • #​2849 72ef7ae6 Thanks @​natemoo-re! - Introduce new astro add command to automatically configure integrations.

    npx astro add

  • #​2833 79545412 Thanks @​natemoo-re! - This PR introduces a new internal CSS parser for @astrojs/compiler. See withastro/compiler#329 for more details.

    This fixes Astro's support for modern CSS syntax like @container, @layer, and nesting. Note While Astro now correctly parses this modern syntax, it does not automatically compile features for browser compatability purposes.

  • #​2824 0a3d3e51 Thanks @​bholmesdev! - Change shiki to our default markdown syntax highlighter. This includes updates to all relevant starter projects that used Prism-specific styles.

Patch Changes

  • #​2879 80034c6c Thanks @​matthewp! - Netlify Adapter

    This change adds a Netlify adapter that uses Netlify Functions. You can use it like so:

    import { defineConfig } from 'astro/config';
import netlify from '@​astrojs/netlify/functions';

export default defineConfig({
	adapter: netlify(),
});

  • #​2871 5029382a Thanks @​FredKSchott! - Fix a bug where tailwind integration wouldn't apply to markdown pages

  • #​2852 96372e6b Thanks @​bholmesdev! - Fix "isSelfAccepting" exception when using the new @​astrojs/react integration in development

  • #​2798 4c25a1c2 Thanks @​matthewp! - Implement APIs for headers for SSR flag

  • #​2855 5e52814d Thanks @​matthewp! - Adds support for the Node adapter (SSR)

    This provides the first SSR adapter available using the integrations API. It is a Node.js adapter that can be used with the http module or any framework that wraps it, like Express.

    In your astro.config.mjs use:

    import nodejs from '@​astrojs/node';

export default {
	adapter: nodejs(),
};

    After performing a build there will be a dist/server/entry.mjs module that works like a middleware function. You can use with any framework that supports the Node request and response objects. For example, with Express you can do:

    import express from 'express';
import { handler as ssrHandler } from '@​astrojs/node';

const app = express();
app.use(handler);

app.listen(8080);

  • #​2859 c781b12f Thanks @​natemoo-re! - Ensure private, internal APIs are not enumerable

  • #​2835 77ebab8b Thanks @​natemoo-re! - Fix missing postcss-load-config dependency

  • #​2878 2db97f10 Thanks @​bholmesdev! - Move the built-in Prism component from astro/components to @astrojs/prism/component.

  • #​2857 1061d647 Thanks @​bholmesdev! - Improve granularity of production build logs. This now lists:

    • the "data collection" build step, with timeout warnings for larger imports. This is useful for understanding large import.meta.glob calls.
    • the Vite client bundling step. This logs all Vite production build info to clarify what assets are built alongside your HTML.
    • the route generation step, complete with all output HTML files for a given input file. This is especially useful when debugging getStaticPaths.
    • fixes "0 pages in Infinityms" log when building to SSR

  • #​2825 1cd7184c Thanks @​hlynursmari1! - Fix island deduplication ignoring props.Re-resolves an issue initially patched in #​846 but seemingly lost in the 0.21.0 mega-merge (d84bfe7).This change makes the component render step account for all props, even if they don't affect the generated HTML, when deduplicating island mounts.

  • #​2873 e4025d1f Thanks @​matthewp! - Improves the build by building to a single file for rendering

  • #​2815 7b9d042d Thanks @​matthewp! - Allows dynamic routes in SSR to avoid implementing getStaticPaths

  • #​2875 55712277 Thanks @​FredKSchott! - Generalize output assets to avoid adblocker false positives

  • #​2848 981e2a83 Thanks @​FredKSchott! - add missing injected "page" scripts into markdown pages

  • #​2872 098f6f6b Thanks @​bholmesdev! - Fix isSelfAccepting errors when using the Preact integration with the Astro dev server

  • Updated dependencies [0a3d3e51, 2db97f10, d763ec18]:

v0.24.1

Compare Source

Patch Changes

v0.24.0

Compare Source

Minor Changes

  • #​2760 77b9c953 Thanks @​bholmesdev! - Introduce a new --host flag + host devOption to expose your server on a network IP

  • af075d81 Thanks @​natemoo-re! - Visual redesign of the astro dev CLI, including new astro --help and astro --version outputs.

    These changes introduce a new startup screen, make it more obvious when a file triggers in-place HMR (update) or a full reload (reload), and improve the way Astro surfaces errors during dev.

  • #​2705 72c2c86e Thanks @​natemoo-re! - New default build strategy

    This change marks the "static build" as the new default build strategy. If you are unfamiliar with this build strategy check out the migration guide on how to change your code to be compatible with this new bulid strategy.

    If you'd like to keep using the old build strategy, use the flag --legacy-build both in your astro dev and astro build scripts, for ex:

    {
	"scripts": {
		"build": "astro build --legacy-build"
	}
}

    Note that the legacy build is deprecated and will be removed in a future version. You should only use this flag until you have the time to migration your code.

  • #​2705 72c2c86e Thanks @​natemoo-re! - ## Updated <head> and <body> behavior

    Since astro@0.21, Astro placed certain restrictions on what files could use <head> or <body> tags. In astro@0.24, the restrictions have been lifted. Astro will be able to correctly handle <head> and <body> tags in any component, not just those in src/pages/ or src/layouts/.

  • #​2747 05b66bd6 Thanks @​natemoo-re! - Escape HTML inside of expressions by default. Please see our migration guide for more details.

Patch Changes

v0.23.7

Compare Source

Patch Changes

v0.23.6

Compare Source

Patch Changes

v0.23.5

Compare Source

Patch Changes

v0.23.4

Compare Source

Patch Changes

v0.23.3

Compare Source

Patch Changes
  • #​2681 046af364 Thanks @​natemoo-re! - Fix HMR regression related to fine-grained .astro HMR. This fixes HMR for Tailwind and CSS styles when .astro files are edited.

v0.23.2

Compare Source

Patch Changes

v0.23.1

Compare Source

Patch Changes

v0.23.0

Compare Source

Minor Changes

  • #​2489 618a16f5 Thanks @​natemoo-re! - Add support for the set:html and set:text directives.

    With the introduction of these directives, unescaped HTML content in expressions is now deprecated. Please migrate to set:html in order to continue injecting unescaped HTML in future versions of Astro—you can use <Fragment set:html={content}> to avoid a wrapper element. set:text allows you to opt-in to escaping now, but it will soon become the default.

  • #​2494 d7149f9b Thanks @​FredKSchott! - Refactor dev server to use vite server internally.

    This should be an invisible change, and no breaking changes are expected from this change. However, it is a big enough refactor that some unexpected changes may occur. If you've experienced a regression in the dev server, it is most likely a bug!

  • #​2586 d6d35bca Thanks @​tony-sull! - Support for non-HTML pages

    ⚠️ This feature is currently only supported with the --experimental-static-build CLI flag. This feature may be refined over the next few weeks/months as SSR support is finalized.

    This adds support for generating non-HTML pages form .js and .ts pages during the build. Built file and extensions are based on the source file's name, ex: src/pages/data.json.ts will be built to dist/data.json.

    Is this different from SSR? Yes! This feature allows JSON, XML, etc. files to be output at build time. Keep an eye out for full SSR support if you need to build similar files when requested, for example as a serverless function in your deployment host.

Examples

```typescript
// src/pages/company.json.ts
export async function get() {
	return {
		body: JSON.stringify({
			name: 'Astro Technology Company',
			url: 'https://astro.build/',
		}),
	};
}
```

What about `getStaticPaths()`? It **just works**™.

```typescript
export async function getStaticPaths() {
    return [
        { params: { slug: 'thing1' }},
        { params: { slug: 'thing2' }}
    ]
}

export async function get(params) {
    const { slug } = params

    return {
        body: // ...JSON.stringify()
    }
}
```

  • #​2424 1abb9ed0 Thanks @​natemoo-re! - Upgrade vite to 2.8.x, unvendoring vite and bringing Astro's dependencies up-to-date.

    This is a low-level change that you shouldn't have to worry about too much, but it should fix many, many issues with CJS/ESM interoperability. It also allows Astro to stay up-to-date with the vite ecosystem. If you run into any unexpected problems, please let us know by opening an issue.

  • #​2471 c9bb1147 Thanks @​FredKSchott! - Standardize trailing subpath behavior in config.

    Most users are not aware of the subtle differences between /foo and /foo/. Internally, we have to handle both which means that we are constantly worrying about the format of the URL, needing to add/remove trailing slashes when we go to work with this property, etc. This change transforms all site values to use a trailing slash internally, which should help reduce bugs for both users and maintainers.

  • #​2548 ba5e2b5e Thanks @​matthewp! - Experimental SSR Support

    ⚠️ If you are a user of Astro and see this PR and think that you can start deploying your app to a server and get SSR, slow down a second! This is only the initial flag and very basic support. Styles are not loading correctly at this point, for example. Like we did with the --experimental-static-build flag, this feature will be refined over the next few weeks/months and we'll let you know when its ready for community testing.

Changes

-   This adds a new `--experimental-ssr` flag to `astro build` which will result in `dist/server/` and `dist/client/` directories.

-   SSR can be used through this API:

    ```js
    import { createServer } from 'http';
    import { loadApp } from 'astro/app/node';

    const app = await loadApp(new URL('./dist/server/', import.meta.url));

    createServer((req, res) => {
      const route = app.match(req);
      if(route) {
        let html = await app.render(req, route);
      }

    }).listen(8080);
    ```

-   This API will be refined over time.

-   This only works in Node.js at the moment.

-   Many features will likely not work correctly, but rendering HTML at least should.
Patch Changes

v0.22.20

Compare Source

Patch Changes

v0.22.19

Compare Source

Patch Changes

v0.22.18

Compare Source

Patch Changes

v0.22.17

Compare Source

Patch Changes

v0.22.16

Compare Source

Patch Changes

v0.22.15

Compare Source

Patch Changes

  • #​2371 85ad1aab Thanks @​natemoo-re! - Add support for styled RSS feeds using the new stylesheet option

  • #​2416 5208c88a Thanks @​matthewp! - Adds Astro.resolve deprecation for the static build

  • #​2392 24aa3245 Thanks @​obnoxiousnerd! - Support markdown draft pages.
    Markdown draft pages are markdown pages which have draft set in their frontmatter. By default, these will not be built by Astro while running astro build. To disable this behavior, you need to set buildOptions.drafts to true or pass the --drafts flag while running astro build. An exaple of a markdown draft page is:

    ---

src/pages/blog-post.md

title: My Blog Post
draft: true
---

This is my blog post which is currently incomplete.
```

v0.22.14

Compare Source

Patch Changes

v0.22.13

Compare Source

Patch Changes

v0.22.12

Compare Source

Patch Changes

v0.22.11

Compare Source

Patch Changes

v0.22.10

Compare Source

Patch Changes

v0.22.9

Compare Source

Patch Changes

v0.22.8

Compare Source

Patch Changes

v0.22.7

Compare Source

Patch Changes

v0.22.6

Compare Source

Patch Changes

v0.22.5

Compare Source

Patch Changes

v0.22.4

Compare Source

Patch Changes

v0.22.3

Compare Source

Patch Changes

v0.22.2

Compare Source

Patch Changes

v0.22.1

Compare Source

Patch Changes

v0.21.13

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 has been generated by Mend Renovate. View repository job log here.

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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants