Astro: [email protected] Release

Release date:
February 1, 2022
Previous version:
[email protected] (released January 29, 2022)
Magnitude:
1,783 Diff Delta
Contributors:
5 total committers
Data confidence:
Commits:

29 Commits in this Release

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

Authored January 31, 2022
Authored January 31, 2022
Authored January 29, 2022
Authored January 29, 2022
Authored January 29, 2022
Authored January 29, 2022
Authored February 1, 2022
Authored January 31, 2022
Authored January 31, 2022
Authored February 1, 2022
Authored January 31, 2022
Authored January 31, 2022
Authored January 31, 2022
Authored January 31, 2022
Authored February 1, 2022
Authored January 31, 2022
Authored January 31, 2022
Authored January 30, 2022
Authored January 29, 2022
Authored January 29, 2022

Top Contributors in [email protected]

ematipico
JuanM04
leerob
jonathantneal
Chrissdroid

Directory Browser for [email protected]

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