rollup-plugin-terser | Rollup plugin to minify generated bundle | Plugin library

Turn out that jest only support ES module export for the project you are working on, anything from the node_modules is not transpile or convert into CJS unless explicitly especify in the jest config.

The easy solution is to add a main field in the package.json pointing to a file that export the modules as CJS wich is what jest can work with, and also having the module field with ES export so webpack can still use the treeshaking and compile time imports etc..

I have fixed this issue. What I did.

So it looks like npm was having troubles? I deleted the node_modules and then used pnpm instead and then ran pnpm install and then pnpm run dev. For some reason it worked!?

It's been almost 2 years since I last used rollup. Anyway in a project I found (where we faced the same issues), I saw the following plugins order:

Looks like DisplayHint is a TS type/interface, not an exported JS value.

Rollup per se is a bundler not a TS language analyzer. It cannot tell if a named export is a concrete JS value or merely a non-existing TS type, thus the reported error.

Rollup plugin order matters. To resolve this specific problem, just lift the typescript plugin up in order, at least before babel. TS plugin, if put to work first, will correctly erase TS type from JS code output.

Update

I know another trick, but it’s a workaround-ish one. The trick is to use import type syntax to explicitly mark DisplayHint as a TS type.

This problem may be caused by the mixing of commonjs require & esm import statements in the same project. Adding transformMixedEsModules to the config of @rollup/plugin-commonjs should help somewhat resolve the issue:

I fixed it by reading the docs.

This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.

The first error:

Was that in the package.json I did not change "main" to the src folder. Just doing that and npm link to peer app node_folders React fixed this problem.

(Just don't forget after "npm run build" of the lib to change back the package.json "main" to src folder.

chnage the .js file to

The storage.child(...) construct is from Firebase SDK 8 and earlier. You can't go mixing and matching that with the new modular/functional syntax of v9.

The equivalent in the new syntax is: