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

Activity

1. oliverjam commented on Feb 7, 2022

   

   oliverjam

   on Feb 7, 2022

   Last edited by oliverjam

   More actions

   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

   on Feb 24, 2022

   Last edited by jordanbtucker

   More actions

   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:

   └─┬ tap@15.0.10
     ├─┬ import-jsx@4.0.0
     │ └─┬ @babel/core@7.15.5
     │   ├─┬ @babel/generator@7.15.4
     │   │ └── source-map@0.5.7 deduped
     │   └── source-map@0.5.7
     ├─┬ nyc@15.1.0
     │ ├─┬ istanbul-lib-instrument@4.0.3
     │ │ └─┬ @babel/core@7.14.8
     │ │   ├─┬ @babel/generator@7.14.8
     │ │   │ └── source-map@0.5.7 deduped
     │ │   └── source-map@0.5.7
     │ └─┬ istanbul-lib-source-maps@4.0.0
     │   └── source-map@0.6.1
     └─┬ source-map-support@0.5.19
       └── source-map@0.6.1
   
3. jordanbtucker commented on Feb 24, 2022

   

   jordanbtucker

   on Feb 24, 2022

   More actions

   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.