Closed tamon-persol closed 2 years ago
Hey @tamon-persol thanks for reporting this bug.
This happens because nextJS generates a bundle on build the app and imports all libraries in a single package. To generate UUID the rich-domain lib uses cripto native in nodejs.
To fix this, the "rich-domain" library needs to expose Crypto compatible with browser. It is native to nodeJS version 14 as higher.
I will work on it.
@tamon-persol you can check the new version v1.12.0
I made this example https://github.com/4lessandrodev/fix-next-rich-domain
Describe the bug I try to use your library with nextJs but it doesn't seem to work.
To Reproduce Steps to reproduce the behavior:
next dev
Screenshots
Lib Version Example: rich-domain v1.1.0
Additional context Add any other context about the problem here.