fix: eslint-config-turbo module export
#10105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In #9976, I erroneously turned the named export from
packages/eslint-config-turbo/index.jsinto a default export inpackages/eslint-config-turbo/index.ts. Users reported the breakage for ESLint v8 projects here.This PR fixes by turning it back into a named export.
Testing Instructions
I've hand-tested the fixed export path with the following steps:
npx create-turbo@latest -e https://github.com/vercel/turborepo/tree/39f94e9af2e51504fa268c92011a96fa04f14190/examples/basic- This is far back enough in history that the example is using ESLint v8.turbo run build --filter=packages/eslint-config-turboon this branchpnpm pack --pack-destination=your-favorite-destinationpackages/eslint-config-package.jsonto the tarball.pnpm installin the example.turbo run lintThat task should pass.
I started feeling pathological about making sure I didn't break it again, so I've also followed the same process for
npx create-turbo@latestfor ensuringeslint-config-turbois working as expected with ESLint v9 Flat Configuration. The diff I used to confirm is (again, make sure to update the dependency path in package.json):