3.0.0 breaks saying "Must use import to load ES Module"

Full error in Next.js (10.1.3)

Server Error
Error: Must use import to load ES Module: /Users/path/to/node_modules/use-sound/dist/index.js
require() of ES modules is not supported.
require() of /Users/path/to/node_modules/use-sound/dist/index.js from /Users/path/to/.next/server/pages/landing.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /Users/path/to/node_modules/use-sound/package.json.

FWIW: It starts working as expected when I remove "type": "module" from the package.json

[joshwcomeau]

Ah, hm. I tested this on my own Next project and it seemed to work, but I see that I get the same error when I try to build, presumably because it converts the import statements to require.

@jlengstorf let me know if you have any ideas for this, I haven’t kept up with module stuff. Thinking for now I’ll revert this change

[joshwcomeau]

3.0.1 removes the type: module field from package.json. I tested on my own Next project and it built, but feel free to let me know if you run into anything else