withastro/astro - CodSpeed

withastro

astro

Blog Docs Changelog

Performance History

Latest Results

Merge branch 'main' into style-import-alias-resolution

style-import-alias-resolution

6 hours ago

Enable native tsconfig path resolution Related: bdeee808c0 Enable Vite's resolve.tsconfigPaths by default so Astro uses the native resolver where it works. Keep the existing custom config alias plugin as a deprecated fallback because testing showed resolve.tsconfigPaths alone does not pass Astro's existing alias suite with the current Vite/Rolldown stack. The fallback comments now explicitly document supported cases: - standalone CSS: @import, @reference, @config, and quoted url() references - Astro <style> preprocessing: the same supported CSS references before preprocessCSS() - module imports: JS/TS/Astro specifiers via resolveId The comments also state the fallback is deprecated and should be removed in a future Astro version once Vite covers these paths. Verification run: - pnpm format - pnpm -C packages/astro run build:ci - pnpm -C packages/astro exec tsc -b - pnpm -C packages/astro exec astro-scripts test "test/{alias-tsconfig,alias-tsconfig-no-baseurl,alias-path-alias-style,alias-css-url}.test.ts"

style-import-alias-resolution

6 hours ago

Update changeset for native tsconfig paths

style-import-alias-resolution

6 hours ago

Resolve tsconfig aliases in Astro style preprocessing Fixes: #17163 Related: 3cf76c035eef5954637e78015be9c20d0129599a, 4766f3716d1e8ee47902bfdf87963a215c462cbe Goal: restore Astro 6-style tsconfig alias handling for CSS references that are written inside .astro <style> blocks and therefore go through Astro's direct preprocessCSS() path instead of Vite's normal transform pipeline. Issue #17163 reported that the earlier CSS alias repair still missed @import url("@/...") and Tailwind-style @reference declarations in component styles. The issue discussion later added @config. Testing resolve.tsconfigPaths showed it is not a replacement here: with Vite 8.1.0/Rolldown 1.1.2 it fails existing Astro alias tests on its own, and even when combined with Astro's custom alias plugin it does not fix the <style> preprocessCSS() path. Decision: keep Astro's existing config alias plugin, extract its CSS alias rewriting into resolveCssAliases(), and call that same helper from createStylePreprocessor before preprocessCSS(). This preserves the standalone .css transform behavior while covering the compiler preprocessing path that previously bypassed the transform hook. The helper now matches @import, @reference, and @config path-bearing at-rules, plus the existing quoted url() handling. It resolves only aliases that map to existing files, matching the previous best-effort behavior. Testing: added an alias-path-alias-style fixture page with @import url('@/styles/base.css'), @reference '@/styles/reference.css', and @config '@/tailwind.config.ts' inside a component <style>. The test asserts the imported CSS is bundled and no @/ alias remains in output CSS. Verification run: - pnpm -C packages/astro run build:ci - pnpm -C packages/astro exec tsc -b - pnpm -C packages/astro exec astro-scripts test "test/{alias-tsconfig,alias-tsconfig-no-baseurl,alias-path-alias-style,alias-css-url}.test.ts" - pnpm format

style-import-alias-resolution

7 hours ago

feat(vite-plugin-html): Replace rehype by ultrahtml

feat/remove-rehype

10 hours ago

chore(head): normalize html charset declarations - Update meta charset from `UTF-8` to `utf-8` across layouts. - Apply the same formatting change consistently in all affected project files. - I first checked `charset="utf-8"` usage which was 191, and for `charset="UTF-8"` it was 57, therefore I've made the change to pick up the lowercase "utf-8" to normalize.

cevdetta:feature/change-charset-declaration-fully-lowercase

13 hours ago

Fix getStaticPaths error in one route blocking other matching routes in dev (#17189) * fix(routing): don't let getStaticPaths errors in one route prevent matching other routes in dev\n\nWhen multiple routes match a URL pattern in dev mode, an error thrown by one\nroute's getStaticPaths() would immediately propagate, preventing other valid\ncandidate routes from being tried. Now the error is stored and the loop\ncontinues; the error is only re-thrown after all candidates are exhausted.\n\nFixes #9819 * test: fix TypeScript errors in dev-match-fallthrough unit test --------- Co-authored-by: Matthew Phillips <matthew@matthewphillips.info>

main

14 hours ago

[ci] format

main

15 hours ago

Latest Branches

-24%

Resolve tsconfig aliases in component style at-rules#17202

6 hours ago

b898aeb

style-import-alias-resolution

feat(vite-plugin-html): Replace rehype by ultrahtml#17199

10 hours ago

f2e385b

feat/remove-rehype

chore(head): normalize html charset declarations#17197

14 hours ago

e5fe5fe

cevdetta:feature/change-charset-declaration-fully-lowercase

Home Terms Privacy Docs