Open crystalin opened 2 years ago
Hi, @crystalin.
The error likely stems from your module resolution strategy (defined as moduleResolution
in your tsconfig). Unless set to NodeNext
or Node16
, the resolution of non-root exports
fails. This is true across Node+TS projects, regardless of Capi usage or lack thereof.
There is a relevant issue I'd like to point out, incase you have a preference on the best path forward. I can imagine other devs will run into this pain point as well, so we certainly need to fine-tune this part of the experience before a first stable release.
We still have some development ahead of us before Capi is ready for the prime time; there will be breaking changes. That being said, testing & feedback is greatly appreciated (thank you!); please let us know how we can ensure Capi ultimately meets your needs.
I following the readme of the repo and ended up with this exemple:
(on node v16)
and ts fails with: