Doug Parker 🕸️Over the last few days while working on an upcoming blog post I've performed quite the yak shaving:
1. I wanted to use `@layer` in a #CSS demo (ironically one showing that it doesn't solve this particular use case).
2. My auto #CSP setup using #JSDom and #CleanCSS failed to parse `@layer`.
3. I upgraded #CleanCSS.
4. I removed #JSDom and replaced it with #parse5, which works with `@layer`.
5. I wanted to use `Object.groupBy` here which requires `target: "ES2024"` in #TypeScript.
6. Therefore I needed to upgrade TS.
7. Upgrading TS broke #Karma for reasons I couldn't understand.
8. Therefore I migrated from Karma to #Vitest (which I've wanted to do anyways).
9. Now #Netlify is confused that I have both an 11ty and Vite project and fails, asking me to pick one.
10. I pick one in `netlify.toml`, but a bug in Netlify refuses to accept it.
Netlify ignores framework configuration and throws "Error: Detected commands for: Eleventy, Vite."
Hi, I have an Eleventy project and recently added Vitest to it for local testing. This seems to confuse Netlify’s deployment which complains that it doesn’t know which one to use: Error: Detected commands for: Eleventy, Vite. Update your settings to specify which to use. Refer to https://ntl.fyi/dev-monorepo for more information. Ok, well that link says I can explicitly specify the framework. So I tried: [dev] framework = "11ty" And: [dev] framework = "Eleventy" But neither of these work a...
icinga (inofficial)