Open stefanwerfling opened 3 months ago
@PupilTong Do you perhaps have a suggestion? Could you leave out "extends Duplex"? What did you think?
@PupilTong Do you perhaps have a suggestion? Could you leave out "extends Duplex"? What did you think?
Could u please inspect which interface requires these implementation? Thank!
Hello @PupilTong, with package.json:
"devDependencies": {
"@types/jmespath": "^0.15.0",
"@types/mocha": "^10.0.1",
"@types/node": "^20.14.10",
"coverage-badge-creator": "^1.0.18",
"inet_xtoy": "^1.2.5",
"mocha": "^10.2.0",
"nyc": "^15.1.0",
"should": "^13.2.3",
"typescript": "^5.2.2"
},
become:
....
Now i check the types:
The "ReadableBase" has more implemented methods. I can all implement with an Exception.
What did you think?
Next problem, i add the method:
public asIndexedPairs(options?: Pick<ArrayOptions, "signal">): Readable {
return undefined;
}
ArrayOptions is unknow and has none export by stream.d.ts ....
It seems to me that the types are faulty. But I can't judge that because I haven't found an example that extends "Duplex".
I have now written "// @ts-ignore" at the top of the class.
With the "// @ts-ignore export class Tuntap extends TuntapBase implements TuntapI {"
I can perform my deployment again.
With the update to the latest 18.x version of nodejs ("@types/node": "^18.19.33",) there were many new methods in the interface. Could you clarify this issue?
These come from the duplex interface:
export interface TuntapI extends Duplex