public record · no signup
●live corpus
withastro/roadmap
What withastro/roadmap's history records
extracted by lema; not reviewed by maintainers
The Astro roadmap — proposals and stage discussions, weighed and rejected in the open.
0 candidates / 0 adjudicated
decisions
865 candidates / 0 adjudicated
ruled out
10,952 candidates / 0 adjudicated
cited claims
Recorded claims
No decisions have been organised from this repository’s history yet — these are individual claims lema extracted, each linked to the discussion it came from.
- An early `astro/icons` proposal was deemed not flexible enough for most uses and was therefore punted on.mined candidatediscussion · 2024-03-25 ↗
- The `astro-icon` approach was not released due to concerns over bloated server bundles.mined candidatediscussion · 2024-03-25 ↗
- Support for `@iconify/json` sets is not an initial goal due to complexities with SSR and tree-shaking.mined candidatediscussion · 2024-03-25 ↗
- Creating framework components for `.svg` icons is considered an anti-pattern due to JavaScript bloat and issues with HMR and client-side performance.mined candidatediscussion · 2023-09-13 ↗
- FredKSchott's early `astro/icons` proposal was not adopted because it was not flexible enough for most uses.mined candidatediscussion · 2023-09-13 ↗
- Releasing `astro-icon` v1 was not pursued due to concerns over bloated server bundles.mined candidatediscussion · 2023-09-13 ↗
- Creating framework components for `.svg` icons is considered an anti-pattern due to JavaScript bloat and performance issues.mined candidatediscussion · 2023-09-06 ↗
- Support for `@iconify/json` sets is not an initial goal due to complexities with SSR and tree-shaking.mined candidatediscussion · 2023-09-06 ↗
- The `astro/icons` proposal was rejected because it was not flexible enough for most uses.mined candidatediscussion · 2023-09-06 ↗
- Creating framework components for .svg icons is considered an anti-pattern due to JavaScript bloat and HMR/client-side performance issues.mined candidatediscussion · 2023-08-28 ↗
- The `astro/icons` proposal was rejected because it was not flexible enough for most uses.mined candidatediscussion · 2023-08-28 ↗
- Creating framework components for `.svg` icons is considered an anti-pattern because it bloats client-side JavaScript and creates headaches for HMR and client-side performance.mined candidatediscussion · 2023-09-06 ↗
- An early proposal for `astro/icons` was rejected because it was not flexible enough for most uses.mined candidatediscussion · 2023-09-06 ↗
- The `astro-icon` approach was not released due to concerns over bloated server bundles.mined candidatediscussion · 2023-09-06 ↗
- Support for `@iconify/json` sets is not an initial goal due to complexities with SSR and tree-shaking.mined candidatediscussion · 2023-09-06 ↗
- Support for `@iconify/json` sets is not an initial goal due to complexities with SSR and tree-shaking.mined candidatediscussion · 2023-08-28 ↗
- The `astro-icon` v1.0 release was withheld due to concerns about bloated server bundles.mined candidatediscussion · 2023-08-28 ↗
- The `astro/icons` proposal was rejected because it was not flexible enough for most use cases.mined candidatediscussion · 2023-08-28 ↗
- The `astro-icon` v1.0 approach was not released due to concerns over bloated server bundles.mined candidatediscussion · 2023-08-28 ↗
- Support for `@iconify/json` sets is not considered a goal for the initial implementation due to complexities with SSR and tree-shaking.mined candidatediscussion · 2023-08-28 ↗