Ben Asher
Ben Asher
It looks like this is still an issue with the latest version. See https://arethetypeswrong.github.io/?p=ajv%408.12.0
@andrewbranch I'm willing/ready to open a PR, but the changes you describe _I think_ only work if we can hand edit the .d.ts. In this case, the .d.ts is generated...
Thanks for that! This gets very close. In resolve.ts, there's now an issue importing the Ajv class type. Here's the import: Here's an example usage:
Draft PR here: #2365 I'm not sure if there is a better way, but I ended up making named exports in two places to make their usages in `export import`...
Adding just that seems to work, but then I go remove the `static default` on the class, and I get this:
And this for each of the `export import` in the non-ambient namespace (the ts error, not the eslint one):
Whooops yes it lol 🤦
Published `@benasher44/ajv`, if folks want to give it a try
Is there a rough ETA for v5 by chance? It'd be great to get this, so we can get the major version graphql-tools updates
👍 just stripping markdown/html comments would be great — should largely solve this common npm case. understandable why you might avoid (1)