question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Namespace 'Webpack' has no exported member 'Compiler'.

See original GitHub issue

I’m submitting a bug report

  • Library Version: 0.31.0

Please tell us about your environment:

  • Operating System: Windows [7|10]

  • Node Version: 8.1.2

  • NPM Version: 5.0.3

  • Browser: all

  • Language: TypeScript 2.4.2

Current behavior: I have problem when I call ‘webpack’ command. 2017-08-19_9-41-40

Namespace 'Webpack' has no exported member 'Compiler'.
Namespace 'Webpack' has no exported member 'Options'.
Namespace 'Webpack' has no exported member 'Parser'.
Namespace 'Webpack' has no exported member 'Compilation'.
Namespace 'Webpack' has no exported member 'Resolver'.
Cannot find name 'DependencyOptionsEx'.
Invalid module name in augmentation. Module 'minimatch' resolves to an untyped module at C:/.../Desktop/aunew/autest/node_modules/minimatch/minimatch.js', which cannot be augmented.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:12 (6 by maintainers)

github_iconTop GitHub Comments

4reactions
pat841commented, Sep 9, 2017

I was able to fix this and avoid any workaround by using “skipLibCheck: true” in my tsconfig.json.

1reaction
searuscommented, Aug 19, 2017

@HamedFathi I managed to fix this by adding an explicit reference to the webpack type definition in tsconfig.js:

  ...
  "exclude": [
    "node_modules",
    "aurelia_project"
  ],
  "files":[
    "./node_modules/@types/webpack/index.d.ts"
  ],
  "filesGlob": [
    "./src/**/*.ts",
    "./test/**/*.ts",
    "./custom_typings/**/*.d.ts"
  ],
  ...

Not sure if this is the correct fix, but it works for me.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Webpack gives me "Module has no exported member..." errors ...
My recommendation is to examine each of your webpack loaders and make sure they are not somehow causing this to happen.
Read more >
Module has no exported member error in TypeScript
The error "Module has no exported member" occurs when we try to import a member that doesn't exist in the specified module. To...
Read more >
Solved: TypeScript compile errors - Esri Community
Solved: I have a basic index.ts file: import ArcGISMap from '@arcgis/core/Map'; ... has no exported member named 'ChainExpression'.
Read more >
TypeStrong/ts-loader - Gitter
and you changed to export over module.exports ? ... does your webpack config not have .ts in the extensions? ... has no exported...
Read more >
'"react-router-dom"' has no exported member named 'redirect'
I'm getting the following error when I attempt to compile an executor. node_modules/@types/react-router-dom/index.d.ts: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found