You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
The documentation in https://turbo.build/repo/docs/handbook/linting/eslint is outdated. In the newly created monorepo, there are no longer an index.js file in packages/eslint-config-custom but a library.js, next.js, and react-internal.js instead. The website doesn't mentioned anything about these files.
Thanks @boompikachu, we're in the middle of re-working these to be more consistent / correct. The code is landing first and the docs will follow shortly!
Thanks @boompikachu, we're in the middle of re-working these to be more consistent / correct. The code is landing first and the docs will follow shortly!
Thank you for an amazing monorepo
By the way, when changing from using index.ts (1.10.12) to next.js (1.10.13) file, will old users know the changes? I'm curious since if I were to init my turborepo now, will I miss out on some of the new features in the future?
What version of Turborepo are you using?
1.10.13
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
The documentation in https://turbo.build/repo/docs/handbook/linting/eslint is outdated. In the newly created monorepo, there are no longer an
index.js
file inpackages/eslint-config-custom
but alibrary.js
,next.js
, andreact-internal.js
instead. The website doesn't mentioned anything about these files.Also, the extended eslint are different; old =
"custom"
new ="custom/next"
which is different from this section: https://turbo.build/repo/docs/getting-started/create-new#understanding-eslint-config-customExpected Behavior
The doc should reflect the monorepo config
To Reproduce
====================
Reproduction Repo
No response
The text was updated successfully, but these errors were encountered: