Danijel Martinek
6fd746d3bd
next.js and react-internal.js are plain re-exports of base, so no rules-of-hooks checking was active anywhere despite three React apps and core-ui. Wire eslint-plugin-react-hooks in base.js scoped to **/*.tsx (non-React packages untouched). Fixes the one violation it surfaced: web-tanstack's root route called Route.useLoaderData inside an anonymous component callback — extracted to a named RootComponent. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
31 lines
758 B
JSON
31 lines
758 B
JSON
{
|
|
"name": "@repo/core-eslint",
|
|
"private": true,
|
|
"version": "0.0.0",
|
|
"type": "module",
|
|
"exports": {
|
|
"./base": "./base.js",
|
|
"./next": "./next.js",
|
|
"./react-internal": "./react-internal.js",
|
|
"./plugin": "./plugin.js"
|
|
},
|
|
"scripts": {
|
|
"test": "vitest run --passWithNoTests"
|
|
},
|
|
"devDependencies": {
|
|
"@eslint/js": "^9.20.0",
|
|
"@typescript-eslint/eslint-plugin": "^8.25.0",
|
|
"@typescript-eslint/parser": "^8.25.0",
|
|
"eslint": "^9.20.0",
|
|
"eslint-config-prettier": "^10.1.0",
|
|
"eslint-plugin-boundaries": "^4.2.2",
|
|
"eslint-plugin-react-hooks": "^5.2.0",
|
|
"eslint-plugin-turbo": "^2.4.0",
|
|
"typescript-eslint": "^8.25.0",
|
|
"vitest": "^3.1.0"
|
|
},
|
|
"dependencies": {
|
|
"globals": "^17.6.0"
|
|
}
|
|
}
|