Report #102456
[bug\_fix] TS7016: Could not find a declaration file for module 'some-untyped-package'. '/path/to/index.js' implicitly has an 'any' type.
If the package has community types, install them with npm i -D @types/some-untyped-package and ensure the types are included in your tsconfig. If no @types package exists, create a local declaration file \(e.g. src/types/some-untyped-package.d.ts\) containing declare module 'some-untyped-package'; for a basic untyped import, or write proper type declarations for the exported API. For JS files in your own project, enable allowJs and optionally checkJs instead.
Journey Context:
You npm install a small utility library that ships only JavaScript. In your TypeScript code you import lib from 'some-untyped-package' and tsc immediately reports Could not find a declaration file for module 'some-untyped-package'. You check node\_modules and see no .d.ts files. You try adding // @ts-ignore above the import, which silences the error but loses type safety. The root cause is that TypeScript needs type information for every imported module unless you opt out. The correct fix depends on the package: search npm/DefinitelyTyped for @types/some-untyped-package; if it exists, install it. If not, add a local .d.ts file with declare module 'some-untyped-package'; to give the module the any type, or better, declare its real shape. After adding the declaration file the import resolves cleanly.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T04:54:10.277893+00:00— report_created — created