search

n9e / fe

Nightingale frontend
Apache License 2.0
176 stars 67 forks source link

main 分支 n9e-fe@v7.4.2 build报错 #1044

Open ytlrr0 opened 1 day ago

ytlrr0 commented 1 day ago 
> n9e-fe@v7.4.2 build
> tsc && cross-env NODE_OPTIONS=--max-old-space-size=6096 vite build

vite v2.9.18 building for production...
transforming...
Module level directives cause errors when bundled, 'use client' was ignored.
Module level directives cause errors when bundled, 'use client' was ignored.
✓ 9474 modules transformed.
[vite]: Rollup failed to resolve import "#minpath" from "node_modules/@uiw/react-markdown-preview/node_modules/vfile/lib/index.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
error during build:
Error: [vite]: Rollup failed to resolve import "#minpath" from "node_modules/@uiw/react-markdown-preview/node_modules/vfile/lib/index.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at onRollupWarning (/var/jenkins_home/workspace/fe/node_modules/vite/dist/node/chunks/dep-0a035c79.js:41797:19)
    at onwarn (/var/jenkins_home/workspace/fe/node_modules/vite/dist/node/chunks/dep-0a035c79.js:41613:13)
    at Object.onwarn (/var/jenkins_home/workspace/fe/node_modules/vite/node_modules/rollup/dist/shared/rollup.js:23216:13)
    at ModuleLoader.handleResolveId (/var/jenkins_home/workspace/fe/node_modules/vite/node_modules/rollup/dist/shared/rollup.js:22466:26)
    at /var/jenkins_home/workspace/fe/node_modules/vite/node_modules/rollup/dist/shared/rollup.js:22427:26
Build step 'Execute shell' marked build as failure
Finished: FAILURE
ytlrr0 commented 1 day ago

我本地清理了如下目录依然报错 rm -rf $WORKSPACE/node_modules rm -rf $WORKSPACE/package-lock.json npm cache clean --force

jsers commented 14 hours ago

rm -rf $WORKSPACE/package-lock.json 这是 react-markdown-preview 包依赖的 vfile 包近期升级导致的问题，基于我们的 package-lock.json 去安装依赖不会报错。