The latest updates on your projects. Learn more about Vercel for Git ↗︎

@jeremy-code is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

The new config is its own folder flat, which seems to be the current standard for maintaining backwards compatability (see eslint-plugin-vue).

I haven't updated eslint-config-turbo, because it is just a default export that extends the config.

I inlined the rules for now since the main export index.ts in eslint-plugin-turbo is where the rules are located, leading to a circular dependency. This may want to be changed in the future. Note that this will cause concerns with caching for those using the config since the metadata property is no longer there -- not certain whether to also inline that or ask whether the code should be rearranged.

Should have no issues in regards to backwards compatability.

This is awesome! 🤩

I hate to ask you for an additional burden, but do you have a monorepo with ESLint v9 in it that I could try to use this against? I still haven't gotten to figure out how ESLint v9 configuration works and I'd like to manually verify this since we don't have any tests.

Alternatively, do you believe there are any tests that we could add to harden the support of the differing versions? (Apologies if this is a naive question.)