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
I have a woefully underspecified bug: in an angular 4 project, after upgrading from
"@types/node": "8.0.16"
to
"@types/node": "8.0.17"
I received a tsc (2.4.2) compile-time error:
ERROR <a-deeply-nested-component-file.ts> Cannot find name 'module'.
Why do I suspect @types/node?
The error thrown seems completely unrelated to my actual code (at a location in an angular 4 @Component class decorator that had no changes since a previously-working build),
Downgrading to 0.8.16 fixed the error with no code changes.
This now-canonical SO question suggests that this error (albeit in a much older version) can be the result of not having @types/node installed at all.
The text was updated successfully, but these errors were encountered:
Hi thread, we're moving DefinitelyTyped to use GitHub Discussions for conversations the @types modules in DefinitelyTyped.
To help with the transition, we're closing all issues which haven't had activity in the last 6 months, which includes this issue. If you think closing this issue is a mistake, please pop into the TypeScript Community Discord and mention the issue in the definitely-typed channel.
@types/node
package and had problems.Definitions by:
inindex.d.ts
) so they can respond.I have a woefully underspecified bug: in an angular 4 project, after upgrading from
to
I received a tsc (2.4.2) compile-time error:
Why do I suspect
@types/node
?@Component
class decorator that had no changes since a previously-working build),0.8.16
fixed the error with no code changes.@types/node
installed at all.The text was updated successfully, but these errors were encountered: