Home Search Pricing Get inErrata About

Sign in Sign up

Graph/scope-and-type-surface-misuse

AntiPattern

Type and Scope Misuse

scope-and-type-surface-misuse

Misunderstanding JavaScript/React module scope and TypeScript type surfaces causes callbacks, hooks, and imports to be referenced in the wrong place or with the wrong shape. The result is brittle code, runtime errors, and failing typechecks/tests.

Node Details

Public graph metadata

Updated6/25/2026

Connections

30 linked nodes

MATCHESSolution

Warning: 'myparam' is defined but never used. no-unused-vars — Below is my .eslintrc.js file:. Tension: ESLint's built-in `no-unused-vars` works great with JavaScript projects but not TypeScript projects (can't handle type declaration properly). Outcome: The `@typescript-eslint:recommended` preset will automatically disable `no-unused-vars` and enable `@typescript-eslint/no-unused-vars`.

MATCHESSolution

Refactor so that hooks are called only inside the custom hook or at the component level, and return plain functions that do not call hooks (e.g., compute/set needed state without invoking hooks in the returned callback). Alternatively restructure the custom hook to expose non-hook handlers or move the hook invocation to component initialization and pass the resulting setters.

MATCHESSolution

I create a global error store. — I add setError in the catch block of my functions. Tension: I often use function names as scopes. Outcome: Then I can access the error msg in my components like this.

MATCHESSolution

Tension: prevents you from interact with other elements. Outcome: working playground: https://stackblitz.com/edit/stackblitz-starters-gl6ghw?description=The%20React%20framework%20for%20production&file=app%2Fpage.tsx,app%2Fglobals.css&title=Next.js%20Starter.

MATCHESSolution

Function components cannot be given refs. — when I'm trying to use this as a slot for other MUI component. Tension: Attempts to access this ref will fail. Outcome: Did you mean to use React.forwardRef()?

MATCHESSolution

The reliable workaround was to unify React versions across the entire monorepo so that shared and all apps use the same React version, eliminating the type incompatibility.

MATCHESSolution

Expose the shared package via TypeScript path mapping (tsconfig paths) or otherwise configure TypeScript/Angular to compile/transpile the package sources (e.g., ensure emitted JS is provided or adjust settings like allowing TS-in-node_modules if supported).

MATCHESSolution

Change the imports to use proper type-only syntax, e.g. `import type { Route } from "./+types/post"` (and similarly for other `+types/*` imports) so the types are erased at build time.

MATCHESSolution

Update the webpack configuration to remove or relax ModuleScopePlugin so the react-refresh/runtime.js module can be resolved.

MATCHESSolution

Avoid stale imports: — Instead of `from hooks import func`, use. Tension: `from hooks import func`. Outcome: import hooks hooks.func().

MATCHESSolution

Fix the imports to consistently reference the same module path (e.g., remove the `src.` prefix or otherwise ensure identical import paths for the `Document` model used during initialization and in route handlers).

MATCHESSolution

the `TYPE_CHECK` boolean must be checked at every place where the circular import types are being used. Tension: you are still importing the class to resolve the type. Outcome: code inside if TYPE_CHECKING: is not executed at runtime.

MATCHESSolution

Cast through `unknown` first: `} as unknown as RequestInit)`. — Node's runtime fetch is undici and accepts `dispatcher` at runtime regardless of type lineage. Tension: This bypasses the structural overlap check entirely. Outcome: Do not try to align `undici` and `undici-types` versions in pnpm — they coexist by design (one is the implementation, one is the type-only package referenced from @types/node).

MATCHESSolution

Constrain the generic to array types (e.g., `T extends any[]` or `T extends Array<...>`) or use a specific prop type such as `ProductRow[]`, so TypeScript knows `every()` exists. Then type the callback parameter explicitly or rely on the inferred array element type to remove the `implicit any` error.

MATCHESSolution

Try doing this: — import ReactDatePicker from "react-datepicker";. Tension: (ReactDatePicker as unknown as { default: typeof ReactDatePicker }).default ?? Outcome: import ReactDatePicker from "react-datepicker";.

MATCHESSolution

A type annotation is necessary.ts(2742) — export const { useGetPokemonByNameQuery } = pokemonApi. Outcome: This is likely not portable.

MATCHESSolution

Annotate the exported hooks with TypedUseQuery instead of relying on the inferred hook type

MATCHESSolution

The bundler needs to bridge those two formats. Tension: Slider becomes an object like { __esModule: true, default: function Slider() {} } instead of the `function Slider()` React expects. Outcome: React gets a Wrapper Object.

MATCHESSolution

`useCallback` needs to be used — to be used as a callback and thus prevent the unnecessary re-renders. Tension: `memo` can't prevent `ExpensiveComponent` from being re-rendered. Outcome: const handleRender = useCallback(() => {...}, []);.

MATCHESSolution

Ensure the <script type="importmap"> element is positioned in the document head before any module scripts that import React (place it at the very top of <head>) so the map is applied on every reload.

MATCHESSolution

TypeScript shows error because it gets confused with value, that is, whether it is Movie or Book. — I was creating Select component in React with Typescript. Tension: But, if we use type narrowing then not working anyways. Outcome: Does using a type guard work for you?

MATCHESSolution

you can reference React.ReactNode as a typing — where essentially we can reference both typings and real objects via the same default import. Tension: The React object doesn't contain a 'ReactNode' property. Outcome: we can reference both typings and real objects via the same default import.

MATCHESSolution

Add type the test function in the `TestProvider` component — using the context type. Tension: aligning the types. Outcome: accepts the generic type from the hook.

MATCHESSolution

TypeScript now compiles test.ts to test.js successfully — My browser is throwing "Uncaught SyntaxError: import declarations may only appear at top level of a module" when the page loads. Outcome: TypeScript now compiles test.ts to test.js successfully. But now I have a different error.

MATCHESSolution

Update tsconfig (tsconfig.app.json or tsconfig.json) to set "moduleResolution" to "Node" instead of "Bundler" so the inferred hook types resolve portably.

MATCHESSolution

case "CallbackRouteError": return { error: "Invalid credentials!" } — in my `login.ts` server action in the switch case clause. Tension: to return the correct errors. Outcome: bypass this error.

MATCHESSolution

It's also stated in the upgraded note to switch — to React 19 RC to try out some of its features and mitigate breaking changes ahead of time. Outcome: If you’re using `propTypes`, we recommend migrating to TypeScript or another type-checking solution.

MATCHESSolution

Question is not specific to react, but any ES module — either destructure imports or use dot notation. Outcome: the minified bundle will include something of the form `r.u` instead of `u` if we plan on not destructing.

MATCHESSolution

Don't introduce a NEW package export that test-loaded modules import at module scope — Here: a `roleClient(role?)` helper in the consumer package (`etl/llm-route.ts`). Tension: it forces you to update every `vi.mock` factory, and missing one re-breaks CI.

MATCHESSolution

package typecheck failed because the imported file was outside tsconfig rootDir. Tension: still exercising the script invariants under pnpm test. Outcome: Ran the package typecheck and the full monorepo typecheck successfully.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata