No "exports" main defined

[yeziluochen]

Describe the bug

A non-existent export error occurred in the vite-plugin-md dependency package while using electrond.
The complete error is reported:
[0] ERROR error when starting dev server:
[0] Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defiVitein C:\Users\Administrator\Desktop\note\vue3-desktop\node_modules.store\vite-plugin-md@0.21.5\node_modules@yankeeinlondon\happy-wrapper\package.json
[0] at new NodeError (node:internal/errors:399:5)
[0] at exportsNotFound (node:internal/modules/esm/resolve:361:10)
[0] at packageExportsResolve (node:internal/modules/esm/resolve:641:13)
[0] at resolveExports (node:internal/modules/cjs/loader:565:36)
[0] at Module._findPath (node:internal/modules/cjs/loader:634:31)
[0] at Module._resolveFilename (node:internal/modules/cjs/loader:1061:27)
[0] at Module._load (node:internal/modules/cjs/loader:920:27)
[0] at Module.require (node:internal/modules/cjs/loader:1141:19)
[0] at require (node:internal/modules/cjs/helpers:110:18)
[0] at Object. (C:\Users\Administrator\Desktop\note\vue3-desktop\node_modules.store\vite-plugin-md@0.21.5\node_modules\vite-plugin-md\dist\index.cjs:18031:28)
[0]
[0] vite exited with code 1

Reproduction

https://gitee.com/yeziluochen/vue3-desktop.git

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400F
    Memory: 3.49 GB / 15.85 GB
  Binaries:
    Node: 18.14.1 - C:\Program\nvm\node\node.EXE
    npm: 9.8.1 - C:\Program\nvm\node\npm.CMD
    Browsers:
    Edge: Chromium (124.0.2478.67)
    Internet Explorer: 11.0.19041.4355

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

[fisher-89]

Add "type":"module" to package.json may solve the problem