Type Errors
See original GitHub issueUsing gluegun 4.2.0 I get the following errors trying to build my project:
node_modules/gluegun/build/types/toolbox/filesystem-types.d.ts:40:36 - error TS2694: Namespace 'path' has no exported member 'resolve'.
40 resolve: typeof import('path').resolve;
~~~~~~~
node_modules/gluegun/build/types/toolbox/prompt-enquirer-types.d.ts:70:34 - error TS2689: Cannot extend an interface 'NodeJS.EventEmitter'. Did you mean 'implements'?
70 declare class BasePrompt extends NodeJS.EventEmitter {
~~~~~~
node_modules/gluegun/build/types/toolbox/prompt-enquirer-types.d.ts:75:44 - error TS2689: Cannot extend an interface 'NodeJS.EventEmitter'. Did you mean 'implements'?
75 declare class Enquirer<T = object> extends NodeJS.EventEmitter {
~~~~~~
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Type I & Type II Errors | Differences, Examples, Visualizations
In statistics, a Type I error is a false positive conclusion, while a Type II error is a false negative conclusion.
Read more >Type I and type II errors - Wikipedia
In statistical hypothesis testing, a type I error is the mistaken rejection of an actually true null hypothesis (also known as a "false...
Read more >What are Type I and Type II Errors? - Simply Psychology
A type 1 error is also known as a false positive and occurs when a researcher incorrectly rejects a true null hypothesis. This...
Read more >Statistics: What are Type 1 and Type 2 Errors? - AB Tasty
Type 1 errors – often assimilated with false positives – happen in hypothesis testing when the null hypothesis is true but rejected.
Read more >Type II Error Explained, Plus Example & vs. Type I Error
A Type II error can be contrasted with a type I error is the rejection of a true null hypothesis, whereas a type...
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 FreeTop 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
Top GitHub Comments
I ran across this same issue recently, it turned out to be a simple typings mismatch, I was running the lts node series v12.16.1 but I had installed @node/types from the 13.x.x series. I updated my package.json to specify version 12.12.30 of @types/node and the problem went away.
I also have a typeerror but i dont know how to solve it: