Typescript: Option resolveJsonModule doesn't work without esModuleInterop
TypeScript Version: 2.9.2, 3.0.0-dev.20180703
Search Terms:
resolveJsonModule, esModuleInterop
Code
import * as test from './test.json';
tsconfig.json:
{
"compilerOptions": {
"module": "commonjs",
"moduleResolution": "node",
"target": "es2017",
"lib": ["es2017"],
"strict": true,
"sourceMap": true,
"noEmitOnError": true,
"baseUrl": ".",
"resolveJsonModule": true,
"outDir": "out"
}
}
Expected behavior:
No errors.
Actual behavior:
Compile error:
$ tsc
test.ts:1:23 - error TS2497: Module '"/home/kostya/tmp/resolve-json-test/test"' resolves to a non-module entity and cannot be imported using this construct.
1 import * as test from './test.json';
~~~~~~~~~~~~~
When I add esModuleInterop option to tsconfig.json:
diff --git a/tsconfig.json b/tsconfig.json
index 7f1afb8..e949135 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -9,6 +9,7 @@
"noEmitOnError": true,
"baseUrl": ".",
"resolveJsonModule": true,
+ "esModuleInterop": true,
"outDir": "out"
}
}
and change import statement to:
diff --git a/test.ts b/test.ts
index 07bb9b7..dddcffb 100644
--- a/test.ts
+++ b/test.ts
@@ -1 +1 @@
-import * as test from './test.json';
+import test from './test.json';
it works. But with esModuleInterop option I need to change many imports in my project, which is undesirable.
Playground Link:
Related Issues:
ikokostya
All 22 comments
Also with resolveJsonModule, but without esModuleInterop, json file appears in output directory.
ikokostya
on 3 Jul 2018
After setting resolveJsonModule to "true", I was having the same issue in VS Code, (TypeScript 3.2.2, VSCode 1.30.1). Restarting VS Code resolved the issue for me - I did not have to alter any other ts config
ne1410s
on 24 Dec 2018
Confirmed that setting resolveJsonModule to true in my tsconfig.json resolved this issue.
faltysad
on 4 Feb 2019
Manually restarting VS Code resolves this issue.
intelliot
on 4 Jun 2019
After setting resolveJsonModule to "true", I was having the same issue in VS Code, (TypeScript 3.2.2, VSCode 1.30.1). Restarting VS Code resolved the issue for me - I did not have to alter any other ts config
Thank you, it worked!
ErnestoIslas
on 21 Jun 2019
After setting resolveJsonModule to "true", I was having the same issue in VS Code, (TypeScript 3.2.2, VSCode 1.30.1). Restarting VS Code resolved the issue for me - I did not have to alter any other ts config
Worked for me as well, thanks!
ps-arndwestermann
on 16 Jul 2019
After setting resolveJsonModule to "true", I was having the same issue in VS Code, (TypeScript 3.2.2, VSCode 1.30.1). Restarting VS Code resolved the issue for me - I did not have to alter any other ts config
This actually worked. Thanks 😃
brionmario
on 11 Aug 2019
After setting resolveJsonModule to "true", I was having the same issue in VS Code, (TypeScript 3.2.2, VSCode 1.30.1). Restarting VS Code resolved the issue for me - I did not have to alter any other ts config
Thanks, It worked like a charm!
redi-monappab
on 27 Oct 2019
I see similar behavior in intellij to what @intelliot described above for vs code. Thanks for the suggestion.
ltomes
on 2 Dec 2019
For those who have updated their target to esnext you need to add the following to your tsconfig:
...
"target" : "esnext",
"moduleResolution": "node",
...
ghost
on 31 Jan 2020
Initially after a restart the file is green, then 3 seconds later highlighted in red again. So restarting in my case doesn't fix this issue.
chrisj-skinner
on 2 Mar 2020
@chrisj-skinner same with me. Not sure why this is happening.
imanuelgittens
on 2 Mar 2020
Why is this issue close since this problem still exists ?
NikosEfthias
on 12 Mar 2020
I have
"esModuleInterop": true,
"resolveJsonModule": true,
"moduleResolution": "node",
and
const pkgJSON = require('../../package.json');
- Consider using '--resolveJsonModule' to import module with '.json' extensionts(2732)
I use resolveJsonModule already.
a-x-
on 16 Mar 2020
If you use WebStorm you shall also restart.
joofholland
on 19 Mar 2020
I have the same issue here,
Initially after a restart the file is green, then 3 seconds later highlighted in red again. So restarting in my case doesn't fix this issue.
Charada32
on 27 Mar 2020
Initially after a restart the file is green, then 3 seconds later highlighted in red again. So restarting in my case doesn't fix this issue.
I had same issue, but that because I forgot to include the new created folder / ts file in the tsconfig.json
axe-me
on 8 Apr 2020
I had same issue, but that because I forgot to include the new created folder / ts file in the tsconfig.json
Same, thanks bro!
clearloop
on 14 Apr 2020
In my case: "File" -> "Invalidate Caches / Restart..." -> "Invalidate and Restart", solved the issue
davide1995
on 5 May 2020
In my case, I fixed this by doing:
"moduleResolution": "node"
This can also fix the issue:
"module": "commonjs"
danmalloc
on 20 May 2020
For my case, I'm unsure if this is suppose to happen or not but, I had to put my tsconfig.json in the same directory as my out and src folders.
SketchyLxve
on 2 Sep 2020
Although I added moduleResolution: node, the error was still there. After a VS restart it got 'fixed'
bujoriosif
on 28 Nov 2020
Related issues
siddjain
·
3Comments
Antony-Jones
·
3Comments
fwanicka
·
3Comments
remojansen
·
3Comments
MartynasZilinskas
·
3Comments
Most helpful comment
After setting resolveJsonModule to "true", I was having the same issue in VS Code, (TypeScript 3.2.2, VSCode 1.30.1). Restarting VS Code resolved the issue for me - I did not have to alter any other ts config