TS errors
See original GitHub issueI’m getting these errors upon building my project:
../node_modules/@types/webpack/index.d.ts(586,28): error TS2507: Type 'typeof "[...]/node_modules/@types/tapable/index"' is not a constructor function type.
../node_modules/@types/webpack/index.d.ts(628,46): error TS2694: Namespace '"[...]/node_modules/@types/tapable/index"' has no exported member 'Plugin'.
../node_modules/@types/webpack/index.d.ts(632,53): error TS2694: Namespace '"[...]/node_modules/@types/tapable/index"' has no exported member 'Plugin'.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Documentation - Understanding Errors - TypeScript
Let's work through some examples to see how they work in practice. Here's an example that produces an error message longer than the...
Read more >TypeScript errors and how to fix them
A list of common TypeScript errors and how to fix them. ... error TS1046: Top-level declarations in .d.ts files must start with either...
Read more >Complete list of Typescript error codes and their fixes
Looking at the 1.6.2 sources of the compiler, tsc.js , tsserver.js , typescript.js and typescriptServices.js , a variable called ts.
Read more >Common TypeScript errors and how to fix them - Payton.Codes
The first thing to keep in mind is that often TS will put the actual problem somewhere near the end of the error...
Read more >ts-error - npm
An extendable Error class that actually works, with TypeScript definition files, supporting old and new style classes and compatibility even ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

following up on @jesion
npm install @types/tapable@0.2.5 --save-devfixes the issueThis appears to be a result of
@types/webpackaggressively getting@types/tapablelatest version 1.0.0.From
@types/webpack(2.2.16) package.json:Which would resolve to semver 1.0.0 according to the list of releases, but as noted above, the “compatible” working version is 0.2.5. When specifying 0.2.5 manually, it works, and the version specification must have been fixed in a more recent version of
@types/webpackaccording to @Brunoon.