feat/v5-collections-deprecation-warnings - Branch - withastro/astro

feat: add deprecation warning for v4 content collections in v5

#14928

Comparing

feat/v5-collections-deprecation-warnings

(

22e658a

) with

main

(

4bceeb0

)

Untouched: 6

Benchmarks

Passed

Rendering: streaming [false], .astro file

benchmark/bench/codspeed.bench.js::Bench rendering

+3%

923.3 ms894 ms

Rendering: streaming [false], .md file

benchmark/bench/codspeed.bench.js::Bench rendering

12.9 ms12.8 ms

Rendering: streaming [true], .mdx file

benchmark/bench/codspeed.bench.js::Bench rendering

721.2 ms721.2 ms

Rendering: streaming [true], .md file

benchmark/bench/codspeed.bench.js::Bench rendering

12.8 ms12.8 ms

Rendering: streaming [false], .mdx file

benchmark/bench/codspeed.bench.js::Bench rendering

713.7 ms715.8 ms

Rendering: streaming [true], .astro file

benchmark/bench/codspeed.bench.js::Bench rendering

938.4 ms942 ms

Commits

Click on a commit to change the comparison range

Base

main

4bceeb0

+0.4%

feat: add deprecation warning for v4 content collections in v5 Emit console warning when collections are defined without a loader, signaling that they're using deprecated v4 backwards compatibility mode. This helps users discover and migrate their legacy collections before upgrading to v6, where the escape hatch will require explicit opt-in with legacy.collectionsBackwardsCompat flag. Warning only shows in dev mode (NODE_ENV !== 'production') to avoid spam in production builds.

453b6e3

8 hours ago

by matthewp

+0.02%

fix build

22e658a

6 hours ago

by matthewp

Home Terms Privacy Docs