Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tsc: ERROR <filename> Cannot find name 'module' after upgrading to 0.8.17 #18425

Closed
4 tasks done
michaelsanford opened this issue Jul 26, 2017 · 1 comment
Closed
4 tasks done

Comments

@michaelsanford
Copy link

michaelsanford commented Jul 26, 2017

  • I tried using the @types/node package and had problems.
  • I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript
  • I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).
  • Mention the authors (see Definitions by: in index.d.ts) so they can respond.

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.
@orta
Copy link
Collaborator

orta commented Jun 7, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants