TypeScript: error TS2339: Property 'debug' does not exist
See original GitHub issueTypeScript reports this error:
node_modules/isomorphic-git/index.d.ts:931:121 - error TS2339: Property 'debug' does not exist on type '{ fs: CallbackFsClient | PromiseFsClient; onProgress?: ProgressCallback | undefined; dir: string; gitdir?: string | undefined; ... 6 more ...; force?: boolean | undefined; }'.
931 export function checkout({ fs, onProgress, dir, gitdir, remote, ref: _ref, filepaths, noCheckout, noUpdateHead, dryRun, debug, force, }: {
~~~~~
Found 1 error.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:24 (15 by maintainers)
Top Results From Across the Web
error TS2339: Property 'x' does not exist on type 'Y'
You can not access indexed properties using the dot notation because typescript has no way of knowing whether or not the object has...
Read more >Getting error TS2339: Property does not exist on type ... - GitHub
This error breaks the notion of TypeScript being a superset of Javascript and any valid JS is a valid TS. 31
Read more >Typescript Type System: How Does it Really Work? Type ...
Let's have a look at the error message we get: Error:(54, 6) TS2339:Property 'name' does not exist on type '{}'. So what is ......
Read more >Property does not exist on type void in TypeScript | bobbyhadz
The "Property does not exist on type void" error occurs when we try to access a property on the return value of a...
Read more >error ts2339: property 'findone' does not exist on type ...
You are trying to access the attribute on the array of LogRepair that is why the error message includes the square brackets after...
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
Thank you. The latest release works without
"DOM"
.Meh. As usual, it’s not really a bug, it’s a feature. All the
@types/*
modules are included by default. Just like how if you don’t specifylib
it includes"DOM"
. (Edit: Well. It might still be a bug, because why should the output change depending on whethercheckJs
is true or not?)By adding
"types": []
to my tsconfig.json file, I am able to prevent the compiler from adding these weirdimport("v8")
references. 🙄Another npm publish coming up…