TypeError: confirm is not a function about msw HOT 7 CLOSED

Hi, @Grohden. Thanks for reporting this!

I can confirm this is an issue on the latest version of MSW that breaks the npx msw init command entirely.

Not sure if the .default import is the right fix though. Need to look deeper into how confirm is bundled. From what I've seen, it's a CJS package.

from msw.

glad I can help a little 🙏

I did the fix locally and at least that command asked for a confirmation for me

from msw.

Is there any solution about this? I have exact problem when doing it in nextjs 14.0.4 - react 18

from msw.

i want to known how to fix it

from msw.

@serabariq @kkkhs specifically for init, just open the file from the stack trace, which is the init.js file:

TypeError: confirm is not a function
    at promptWorkerDirectoryUpdate (<path here>/node_modules/msw/cli/init.js:183:10)
    at Object.init [as handler] (<path here>/node_modules/msw/cli/init.js:45:7)

and change the inquirer import at the top of the file to have .default at the end:

const confirm = require('@inquirer/confirm').default

from msw.

I'm also running into this issue, and it's a bit of a blocker. Would love for a fix to get prioritized.

from msw.

Released: v2.2.4 🎉

This has been released in v2.2.4!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.

from msw.