Production environment library method does not exist

[huzedong2015]

Describe the bug

Production environment htmldiff execute function is undefined

Reproduction

https://stackblitz.com/edit/vitejs-vite-pisuhy?file=main.js

System Info

null

Used Package Manager

pnpm

Logs

$ vite build
$ cd dist
$ pnpx live-server

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[huzedong2015]

Code

import htmlDiff from "htmldiff-js";

development

htmlDiff is class v

production environment

htmlDiff is { default: class v, __esModule: true }

[huzedong2015]

Check the @rollup/plugin-commonjs document. It should be possible to configure the defaultismoduleexports option to false, but vite.config. js build. Commonjsoptions does not have this configuration

[huzedong2015]

I found that vite config. js build. commonjsOptions. Defaultismoduleexports is set to false, and the production environment can run normally，But I don't know if it will bring other problems

[davbrito]

The workaround that I did for this issue was to do something like:

import $htmlDiff from "htmldiff-js";
const htmlDiff = $htmlDiff.default || htmlDiff

But it feels a little bit tricky. So I hope you can solve this problem soon.

[huzedong2015]

The workaround that I did for this issue was to do something like:

import $htmlDiff from "htmldiff-js";
const htmlDiff = $htmlDiff.default || htmlDiff

But it feels a little bit tricky. So I hope you can solve this problem soon.

I think this can only be used as an emergency measure, which should be handled by the plug-in to keep the dev and pro environments consistent

[Young6-me]

Other dependencies I also encountered this similar problem

[AmyLoveLife]

I have the same situation，please solve it soon

[chocking]

+1, Occured this when using lib mode for product build, and my module imports a commonJS module meanwhile.

[bluwy]

I can't reproduce this anymore with Vite 4.5.0. It might be fixed the same way as #2139 (comment). In dev and prod, I'm getting the class directly. Closing as fixed.