Jeremy Nguyen

The new config is its own folder `flat`, which seems to be the current standard for maintaining backwards compatability (see [eslint-plugin-vue](https://github.com/vuejs/eslint-plugin-vue/tree/master/lib/configs/flat)). I haven't updated [eslint-config-turbo](https://github.com/vercel/turbo/blob/main/packages/eslint-config-turbo/index.js), because it is just a...

Will be working on this, will open a new PR when done

Previous PR was #8054, @anthonyshew

@anthonyshew Sorry, I didn't realize y'all were blocked on me. I have fixed any conflicts. Let me know if there's any issues. I ran the test suite again and saw...

 Oh so that's what you meant by example repo -- I thought you just meant the ESLint config file. The above is a quick and (very) dirty proof of...

Did you run pnpm run build beforehand (or more specifically tsup in packages/eslint-plugin-turbo)? I just straight up copied-pasted all the code necessary for the ESLint plugin just for a quick...

Nono I am pretty certain it's my fault I thought (hoped?) I fixed these merge issues since the original commit was a bit of time ago. Let me see if...

As an aside, for a quick fix, you can downgrade to `[email protected]` since the following version introduces #429 which makes array imports fail fast (as expected) instead of falling back...

Related: #30716

A workaround that involves not using aliases is using [Node.js self-referencing](https://nodejs.org/api/packages.html#self-referencing-a-package-using-its-name). For instance, see the following code: ```jsonc // package.json { "name": "@repo/ui", "exports": { "./globals.css": "./globals.css", "./postcss.config": "./postcss.config.js", "./tailwind.config":...