Open andymatuschak opened 4 years ago
@andymatuschak thanks for reporting this. It appears that is caused by a bug in typescript's type declaration generation code https://github.com/microsoft/TypeScript/issues/41258, it seems to loose type parameters for jsdoc @implements
comment. E.g last error on line 64 is generated from:
@andymatuschak do you still observe compliation with skipLibCheck
enabled ? I have not tested that, but I believe it should not cause problems when that option is enabled.
If skipLibCheck
does not solve this problem, we could just remove all the @implements
, but I would much rather not so we can ensure implementations don't diverge.
@Gozala Nice work reducing the TypeScript issue—looks like they plan to fix it in 4.2.0, so hopefully this won't be an issue long.
Indeed, setting skipLibCheck
does solve the problem for me, so that's a good workaround! I don't want to leave that enabled for my project, since I have some other local type definitions, and I want those to be type checked. But at least others can use that workaround.
Should we put a note about this gotcha and its workaround in the Readme until the issue's fixed? Happy to submit a PR for that if it's welcome; if not, let's just close and move on.
Should we put a note about this gotcha and its workaround in the Readme until the issue's fixed? Happy to submit a PR for that if it's welcome; if not, let's just close and move on.
That would be amazing thanks!
Hi, all. The generated .d.ts files are missing some generic arguments, making builds fail when using these type definitions. For instance, in
base.d.ts
:MultibaseDecoder
andCombobaseDecoder
both require aPrefix
generic type argument, but none is supplied.This is the full set of errors I encountered, but it may not be exhaustive, since I'm not importing all submodules: