Skip to content

Visual Studio cannot find Typescript declaration file 'source-map' #449

Description

@Edminsson

I'm getting this error in Visual Studio 2019 :

Error TS6053 File 'path-to-my-project/node_modules/source-map/source-map' not found.
The file is in the program because: Root file specified for compilation

The cause of this error seems to be this line in package.json:
"typings": "source-map",
If i change it to
"typings": "source-map.d.ts",
then everythings works fine.

Activity

  1. oliverjam commented on Feb 7, 2022

    @oliverjam

    Looks like this was fixed in 2018. I had the same error; one of my dependencies depends on a much older version of source-map. It's probably fixable by using "overrides" in your package.json (as of npm version 8) to set a newer version of this library.

  2. jordanbtucker commented on Feb 24, 2022

    @jordanbtucker

    For me, this issue was occurring because @babel/generator still uses source-map@^0.5.0. They actually bumped the version two years ago, but then reverted it due to a regression (rather than fixing their codebase to work with the new version of source-map).

    See: babel/babel#12025

    If you run npm ls source-map you can see the tree of which packages are dependent upon it. Here's what mine looks like:

    └─┬ [email protected]
      ├─┬ [email protected]
      │ └─┬ @babel/[email protected]
      │   ├─┬ @babel/[email protected]
      │   │ └── [email protected] deduped
      │   └── [email protected]
      ├─┬ [email protected]
      │ ├─┬ [email protected]
      │ │ └─┬ @babel/[email protected]
      │ │   ├─┬ @babel/[email protected]
      │ │   │ └── [email protected] deduped
      │ │   └── [email protected]
      │ └─┬ [email protected]
      │   └── [email protected]
      └─┬ [email protected]
        └── [email protected]
    
  3. jordanbtucker commented on Feb 24, 2022

    @jordanbtucker

    Maybe the fix can be backported into ^0.5 and ^0.6. I think this repo would need to create a branch for each of those minor versions before I could create a PR for them though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions