-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requiring node core module with trailing slash /
ERROR
#67
Comments
This is fixed in Updated repro: https://stackblitz.com/edit/github-yd3jt3-9mmv9s?file=package.json |
Thanks a lot for the quick fix. The trailing slash issue is indeed fixed in the new version. However, the nuxt production build is still failing for me with a different error from #41. Now, the Reproduction: https://stackblitz.com/edit/github-yd3jt3?file=nuxt.config.ts
The reproduction uses nuxt 3.8.2 (which is the version I am currently using) but I have also tested the latest 3.9.0 release (which leverages vite 5.x) and no luck either. Let me know if I could expect any help from the plugin side. Thanks in advanced! |
Just posting here that I was able to fix my issue thanks to the awesome guys at nuxt. In the end, it was just a matter of targeting a different polyfill library in the aliasing property. Here is some context in case you find it useful. Thanks for the plugin!! |
@davidmyersdev I would be more than happy to help if you like to migrate the polyfill backend to unenv, it should make the plugin much more usable. |
Hey @pi0! I would love to migrate to |
@davidmyersdev
My original post here
As pointed in the previous thread, seems like the plugin fails due to an upstream dependency trying to import
process/
instead ofprocess
.Doing some digging I detected that the conflicting dependency was
readable-stream
which is a NodeJS official package. Looks like the trailing slash/
syntax is intended... as explained here.Do not really understand the rationale behind it since it feels like a workaround for browserify...
In any case, it would be great if we can expect a fix from the plugin side.
Thanks a lot for your help!
The text was updated successfully, but these errors were encountered: