-
Notifications
You must be signed in to change notification settings - Fork 230
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
Incompatibility with Rollup/Vite process polyfill #539
Comments
Thanks for reporting! Can you provide steps to reproduce? We often need a reproducible example, e.g. some code that allows someone else to recreate your problem by just copying and pasting it. If it involves more than a couple of different file, create a new repository on GitHub and add a link to that. |
Here you are! ^_^ |
I've added a GitHub pages deployment, pressing the button should cause a console error. |
Any apdate ? |
This package seems to require const process = require('process/') Perhaps |
I noticed #497 since it is somewhat related. I recall editing the package to replace On the TSC note I realized that my example was missing |
In the absence of any new insight, I've made a brute-force fix on this branch. For what it's worth, all tests pass and it works perfectly in the reprex. To try it out:
(cc. @Gitssalah) |
I'll be happy to land a PR covered by tests. |
Use |
Similar to #450, though in this case a polyfill is present. It looks like the
process
polyfill is an ES module with a default export that isn't being properly unwrapped byreadable-stream
.I've set a breakpoint on the line that is causing
TypeError: e.nextTick is not a function
:I can confirm that a
nextTick
implementation is available at both thedefault
andprocess
fields. Here myvite.config.ts
:readable-stream
^4.5.2
vite
^5.4.2
vite-plugin-node-polyfills
^0.22.0
rollup
^4.21.0
esbuild
^0.23.1
The text was updated successfully, but these errors were encountered: