error TS1192: Module '" A.module"' has no default export

Question

I have created a new module 'A' and trying to import it in another module called 'B'. I am getting this error on compiling that says

error TS1192: Module '" A.module"' has no default export

Can anyone please help on how to solve this error.

Does this answer your question? [Module has not default export after converting to Typescript](https://stackoverflow.com/questions/55870154/module-has-not-default-export-after-converting-to-typescript) — Michael Freidgeim, Sep 28 '20 at 23:20

score 291 · Accepted Answer · edited Dec 24 '22 at 08:58

291

This was a simple error. It occurred due to the missing {} around the module name in the import statement itself.

edited Dec 24 '22 at 08:58

starball

20,030
7
43
238

answered Nov 04 '16 at 19:33

Abhi

4,553
4
16
22

11

jeez. thanks... just FYI, this is whats going on lol... WRONG: import YourWhateverThing from './your-whatever-file.component.' RIGHT: import {YourWhateverThing} from from './your-whatever-file.component.' – Andy Danger Gagne Jun 28 '17 at 15:06
Note: This answer was added at the very initial stages of Angular 2. Please check your version and solution accordingly, since this may not work for all the similar issues as mentioned by other kind people. Cheers. – Abhi Feb 21 '22 at 03:19

score 156 · Answer 2 · answered May 22 '18 at 17:16

156

Accepted answer didn't work for me, so I am posting more info.

I had:

import Module from 'module';

and this worked for me:

import * as Module from 'module';

src: https://github.com/Microsoft/TypeScript/issues/3337#issuecomment-107971371

answered May 22 '18 at 17:16

nothing-special-here

11,230
13
64
94

3

jeez, lucky I found this. Thanks guys! – Radityo Ardi Feb 04 '21 at 10:38
Thank you! To use import X from 'xPath', then there needs to be an export default. But if there is export default, then we use import * as X from 'xPath'. Wow! – Thuy Aug 26 '21 at 20:53
Oh wow I feel dumb. TS was complaining about not having default exports and this was the way to go, made them all named and then imported them all so i could do ComponentName.NamedComponent – Lauren Dec 01 '22 at 14:50

score 34 · Answer 3 · answered Nov 19 '19 at 11:47

34

For me this issue was addressed using "allowSyntheticDefaultImports": true within compilerOptions in the project's tsconfig.json.

Our specific error related to a moment js import.

More about this option can be found here

answered Nov 19 '19 at 11:47

Michael Hancock

2,673
1
18
37

4

This is the only correct option when using TypeScript to type-check plain JavaScript. If anyone else comes across this, remember to restart the language service (VS Code: Ctrl/Cmd+Shift+P > TypeScript: Restart TSServer) after updating tsconfig.json if the option does not seem to come into effect immediately. – Tomáš Hübelbauer Mar 28 '21 at 13:07
@TomášHübelbauer adding the key/value to compileroptions with restart of tsserver in vscode did not help, but [`import * as foo from 'bar'`](https://stackoverflow.com/a/50473239/1705829) helped. – Timo Aug 07 '22 at 06:44
1

This worked for me. Thanks. – Ronn Wilder Jun 15 '23 at 05:17

score 23 · Answer 4 · answered Apr 16 '19 at 08:15

23

Use:

import { Module } from 'module';

You need to insert the module name between {...}

answered Apr 16 '19 at 08:15

Rafael Tovar

239
2
3

score 8 · Answer 5 · answered May 18 '21 at 20:21

8

I fixed it by adding this to tsconfig.json in my angular project.

{
  ...
  "compilerOptions": {
    ...
    "allowSyntheticDefaultImports": true,

answered May 18 '21 at 20:21

tbo47

2,688
3
20
11

score 4 · Answer 6 · answered Jul 25 '21 at 11:43

4

I fixed above issue by putting the following inside the tsconfig.json file:

{
  "compilerOptions": {
    ...
    "esModuleInterop": true
    ...
  }
}

answered Jul 25 '21 at 11:43

ziishaned

4,944
3
25
32

1

Worked for me. Weird that this answer has like the least amount of votes. – Constantine Ketskalo Mar 02 '23 at 19:27

score 1 · Answer 7 · answered Dec 13 '19 at 15:38

1

Instead of importing it as module, you can also require it like so:

const Module = require('./some_folder/module');

module.ts would then have:

module.exports = class Module {
    ... your module code
}

answered Dec 13 '19 at 15:38

José Veríssimo

221
2
11

score 1 · Answer 8 · answered Oct 02 '20 at 16:49

All above answers didn't solve my error. Below solution worked for me. Before this, I have run below command

npm i @types/moment-timezone --save-dev

And then I imported moment like below in .ts file.

import * as moment from "moment-timezone";

I hope, it will help someone. Thanks!

score 0 · Answer 9 · answered Feb 21 '23 at 15:52

0

To solve this problem, instead of exporting the module as named export, we need to make it a default exported module as below

export default class Module {
    ... your module code
}

answered Feb 21 '23 at 15:52

Suchismita Goswami

61
5

error TS1192: Module '" A.module"' has no default export

9 Answers9

Linked