Guillaume Renard

Yeah this still happens with latest versions. That is... huh... dangerous. I hope this one get fixed

I'm also seeing the same issue in my CRA project. Many unrelated dependencies get updated after running either `npx update-browserslist-db@latest` or `pnpm dlx update-browserslist-db@latest` (the project uses PNPM):  EDIT:...

Ohh OK, looks like it's a known issue with PNPM: https://github.com/pnpm/pnpm/issues/5118 My CRA project doesn't have a direct dependency on `caniuse-lite`, so it seems that `pnpm up caniuse-lite` is just...

Adding the following code to my vitest setup file did the trick for me: ```ts import { TextDecoder, TextEncoder } from 'node:util'; Object.defineProperties(globalThis, { TextDecoder: { value: TextDecoder }, TextEncoder:...

Looks like you need to update webpack-cli to a more recent version (see https://github.com/webpack/webpack-cli/issues/2894#issuecomment-2251131291). This did the trick in `webpack-mf/package.json` : ```diff - "webpack-cli": "4.10.0" + "webpack-cli": "5.1.4" ``` Also...

Just a thought / suggestion: if Axios exported its default instance via a named export too, we could stop relying on the default export and write this directly, which would...

As a workaround, I was able to force webpack to load the CommonJS version of my package. It works because it finds the `axios.default` instance which the CJS version of...

I found another workaround when bundling with `tsup`. I think `tsup` itself is having issues with `default` exports in CJS modules. In order to avoid these issues (`axios__WEBPACK_IMPORTED_MODULE_0__.create is not...

Hey, is there any workaround for [this issue](https://github.com/mswjs/data/issues/306#issuecomment-2897871744) while support is being added? I'm not too sure how to make the changes mentioned on the link when using vitest +...