Closed ohueter closed 1 year ago
Fixed here: https://github.com/getlago/lago-javascript-client/pull/12
You'll have to wait till the next Lago release for this to make it to npm since npm doesn't let you publish to the same version and the Lago team wants the version to be in sync with the main Lago product.
I recommend patch-package in the meantime
Thanks a lot for fixing this so quickly! 🚀
You'll have to wait till the next Lago release for this to make it to npm since npm doesn't let you publish to the same version and the Lago team wants the version to be in sync with the main Lago product.
There seems to be a patch version field in your versioning scheme. As this seems to be the first bug issue in this repo, maybe this would be a good opportunity to begin using it? :)
You could ask the Lago team in Slack, they originally told me they wanted SDK versions pinned to the main Lago release
Hey,
Thanks both for raising and fixing this issue.
A new version of this client is available with the bugfix
0.26.1-beta
I'm getting the following build error when using
lago-javascript-client
in a Node 18 / Next.js / TypeScript / pnpm project:The fix is to reverse the order of
types
anddefault
exports in thepackage.json
of this library, just as the error says:Compare the documentation on this property:
From: https://nodejs.org/api/packages.html#conditional-exports
Would you accept a PR for this fix?