Home » Oreps » Astro » All Releases » astro@0.23.0-next.0 Release
withastro/astro
The web framework for content-driven websites. ⭐️ Star to support our work!
Watch
0
Commit Activity
Directory Browser
Velocity History
Releasesastro@0.23.0-next.0
Basic Details Issues Addressed Top Contributors Directory Browser Release Notes
Astro astro@0.23.0-next.0

Astro: astro@0.23.0-next.0 Release

Release date:
February 1, 2022
Previous version:
astro@0.22.20 (released January 29, 2022)
Magnitude:
2,239 Diff Delta
Contributors:
5 total committers
Data confidence:
Commits:
29 impacting commits

29 Commits in this Release

Ordered by the degree to which they evolved the repo in this version.

refactor dev to use vite server (#2494)
Authored January 31, 2022
Add Shiki as an alternative to Prism (#2497)
Authored January 31, 2022
Deprecate unescaped HTML inside of expressions (#2489)
Authored January 31, 2022
[MINOR] standardize trailing subpath, fix fetchContent url issue (#2471)
Authored January 29, 2022
Update deployment documentation for Vercel. (#2500)
Authored January 31, 2022
Fix issue rendering content within HTMLElement (#2506)
Authored January 31, 2022
Enter prerelease mode (#2510)
Authored January 31, 2022
Add Astro.resolve deprecation warning case for script tags (#2493)
Authored January 31, 2022
Fix define:vars in the static build flag (#2511)
Authored January 31, 2022
Fix a regression in vite.build() base option (#2502)
Authored January 31, 2022
remove old docs template
Authored January 29, 2022
Handle project folders containing a space in the static build (#2486)
Authored January 29, 2022
point issues to the new docs repo
Authored January 29, 2022
[ci] yarn format
Authored January 29, 2022
update turbo config
Authored January 29, 2022
update congratsbot again
Authored February 1, 2022
Minimize the minimal example (#2508)
Authored January 31, 2022
Fix Astro Components example (#2507)
Authored January 31, 2022
update congratsbot format again
Authored February 1, 2022
Remove SVG animation on GitHub/NPM (#2512)
Authored January 31, 2022
[ci] yarn format
Authored January 31, 2022
[ci] yarn format
Authored January 31, 2022
[ci] update lockfile (#2495)
Authored January 31, 2022
[ci] collect stats
Authored February 1, 2022
[ci] yarn format
Authored January 31, 2022
[ci] collect stats
Authored January 31, 2022
[ci] collect stats
Authored January 30, 2022
[ci] collect stats
Authored January 29, 2022
[ci] yarn format
Authored January 29, 2022

Browse Other Releases

Latest Pending Unreleased 😎
astro@0.23.0-next.5 Released February 11, 2022
73 Ξ”
astro@0.23.0-next.4 Released February 9, 2022
99 Ξ”
astro@0.23.0-next.3 Released February 8, 2022
114 Ξ”
astro@0.23.0-next.2 Released February 7, 2022
1,593 Ξ”
astro@0.23.0-next.1 Released February 2, 2022
262 Ξ”
astro@0.23.0-next.0 Released February 1, 2022
2,239 Ξ”
astro@0.22.20 Released January 29, 2022
249 Ξ”
astro@0.22.19 Released January 27, 2022
424 Ξ”
astro@0.22.18 Released January 24, 2022
334 Ξ”
astro@0.22.17 Released January 21, 2022
400 Ξ”

Top Contributors in astro@0.23.0-next.0

ematipico
JuanM04
leerob
jonathantneal
Chrissdroid

Directory Browser for astro@0.23.0-next.0

We haven't yet finished calculating and confirming the files and directories changed in this release. Please check back soon.

Release Notes Published

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!

  • #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.

Patch Changes