How to configure ESLint in a Turborepo monorepo to avoid tsconfigRootDir errors

Update Framework settings labeling to include sveltekit 2

`use-node-version` not supported

`vercel env pull` adds quotes to the output file

How to configure ESLint in a Turborepo monorepo to avoid tsconfigRootDir errors

Thanks for pointing me in the right direction. I followed your advice and it worked. I did make some adjustments though. According to...

How to configure ESLint in a Turborepo monorepo to avoid tsconfigRootDir errors

* I often get `tsconfigRootDir` errors? * Should I have a root level `eslint.config.js`? * Why was `extends` used [here](https://github.com/vercel/turborepo/blob/main/examples/kitchen-sink/packa

Update Framework settings labeling to include sveltekit 2

Vercel should add a V2 or update the V1 label to include V2

`vercel env pull` adds quotes to the output file

bump bump bump bump (post must have at least 20 characters)

`use-node-version` not supported

What is the purpose of this limitation? In the meantime, I have a workaround by deleting that line during CI ```json // package.json { scripts: { "deploy": "node ../scripts/deleteUseNodeVersio

`use-node-version` not supported

The behaviour isn't the same. `engine-strict` limits the node version I can use. But `use-node-version` automatically sets my node version to the correct one.

`use-node-version` not supported

Ya, that's what I use to manage node versions in dev via pnpm

`use-node-version` not supported

<!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand...

`vercel env pull` adds quotes to the output file

<!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand...