David Myers
David Myers
This relates to #16. I think the best approach here is to use the new `overrides` feature to specify a better polyfill for `path` that meets your specific use case.
Ah, that makes sense. I think `fs` runs into the same problem with `fs/promises` not playing well with packages like `memfs` that do not specify subpath exports. I'll see if...
I've started looking into this, and I found a temporary workaround. Add a custom `alias` to your Vite config that points to the corresponding polyfill: ```ts import { defineConfig }...
Hey @Miniontoby. Would you mind adding a reproducible example via Stackblitz or similar? Without it, it's hard for me to debug the problem.
@RandomGuyInLife I unfortunately can't dedicate time toward issues without functional reproducible examples. If you're running into a similar error and can provide one, then I can take a look. Based...
Hey @winixt. Would you mind adding a reproducible example via Stackblitz or similar?
I'm closing this for now. If a reproduction of the issue is provided, I'll reopen it.
Hey @artursapek. 👋 I just ran the tests, and it looks like some are failing and need to be updated. Would you mind updating those? I can merge once CI...
@Ilyat1337 It looks like that error is actually being raised by the `fs` module due to its reliance on `process`. I'll have to split those tests up.
@jsoneaday it looks like you are externalizing the shims for `buffer`, `global`, and `process`. Without a full reproduction, I can't diagnose the problem or provide a fix.