Update tsconfig.json

[jameshfisher]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)
• If applicable, I’ve added docs and tests

Description of changes

Fix issue described in #6

[ChristianMurphy]

Thanks @jameshfisher!
node16 module resolution is something making its way through the ecosystem, but hasn't reached here yet.
Thanks for looking into it.

A couple items to get it across the finish line.

1. Could you update the ts config of this project to use node16 resolution (using the same config options elsewhere https://github.com/syntax-tree/mdast-util-assert/blob/8958dff406cb658abc4189568ed7af2c56d9320c/tsconfig.json)
2. Could you look into the type error currently breaking CI? (which may require going to some of this project's dependencies and updating them to support node16 mode as well)

[wooorm]

Yup, you should be able to port this commit: syntax-tree/mdast-util-assert@8958dff. And things will work :)

[jameshfisher]

@wooorm I've ported that commit, updated some dependencies, and tried to resolve some broken references in imports. It still has lots of type-checking errors though, and I don't know how to resolve them.

(It doesn't help that my laptop explodes and takes 15+ seconds for types to update when making any single-character changes in VS Code. This seems to be associated with instances of visit causing some perverse worst-case in type-checking. Any advice on this weird problem appreciated!)

[remcohaszing]

Thank you! Just 2 small suggestions

[wooorm]

Thanks!

[wooorm]

Released in 2.2.3!