-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Closed as not planned
Description
Describe the bug
when exec npm run dev , on vite pre-bundling dependencies,it throw err, it auto add './' to the head of module path,like
dep:Vuex:1:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vuex/dist/vuex.esm-bundler.js"
Reproduction
https://github.com/Allenscript/vite_demo
System Info
System:
OS: Windows 7 6.1.7601
CPU: (4) x64 Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz
Memory: 3.37 GB / 7.93 GB
Binaries:
Node: 14.17.5 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.11 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.14 - C:\Program Files\nodejs\npm.CMD
Browsers:
Internet Explorer: 11.0.9600.18763
npmPackages:
@vitejs/plugin-vue: ^1.2.2 => 1.4.0
vite: ^2.2.3 => 2.5.0Used Package Manager
npm
Logs
$ vite --debug
vite:config native esm config loaded in 434ms URL {
href: 'file:///C:/Users/Administrator/Desktop/code/Solution/front/vite.config.js',
origin: 'null',
protocol: 'file:',
username: '',
password: '',
host: '',
hostname: '',
port: '',
pathname: '/C:/Users/Administrator/Desktop/code/Solution/front/vite.config.js',
search: '',
searchParams: URLSearchParams {},
hash: ''
} +0ms
vite:config using resolved config: {
vite:config plugins: [
vite:config 'vite:pre-alias',
vite:config 'alias',
vite:config 'vite:modulepreload-polyfill',
vite:config 'vite:resolve',
vite:config 'vite:html',
vite:config 'vite:css',
vite:config 'vite:esbuild',
vite:config 'vite:json',
vite:config 'vite:wasm',
vite:config 'vite:worker',
vite:config 'vite:asset',
vite:config 'vite:vue',
vite:config 'vite:define',
vite:config 'vite:css-post',
vite:config 'vite:client-inject',
vite:config 'vite:import-analysis'
vite:config ],
vite:config server: { fs: { strict: undefined, allow: [Array] } },
vite:config define: { __VUE_OPTIONS_API__: true, __VUE_PROD_DEVTOOLS__: false },
vite:config ssr: { external: [ 'vue', '@vue/server-renderer' ] },
vite:config configFile: 'C:/Users/Administrator/Desktop/code/Solution/front/vite.config.js',
vite:config configFileDependencies: [],
vite:config inlineConfig: {
vite:config root: undefined,
vite:config base: undefined,
vite:config mode: undefined,
vite:config configFile: undefined,
vite:config logLevel: undefined,
vite:config clearScreen: undefined,
vite:config server: { fs: [Object] }
vite:config },
vite:config root: 'C:/Users/Administrator/Desktop/code/Solution/front',
vite:config base: '/',
vite:config resolve: { dedupe: undefined, alias: [ [Object], [Object] ] },
vite:config publicDir: 'C:\\Users\\Administrator\\Desktop\\code\\Solution\\front\\public',
vite:config cacheDir: 'C:\\Users\\Administrator\\Desktop\\code\\Solution\\front\\node_modules\\.vite',
vite:config command: 'serve',
vite:config mode: 'development',
vite:config isProduction: false,
vite:config build: {
vite:config target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
vite:config polyfillModulePreload: true,
vite:config outDir: 'dist',
vite:config assetsDir: 'assets',
vite:config assetsInlineLimit: 4096,
vite:config cssCodeSplit: true,
vite:config sourcemap: false,
vite:config rollupOptions: {},
vite:config commonjsOptions: { include: [Array], extensions: [Array] },
vite:config dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] },
vite:config minify: 'terser',
vite:config terserOptions: {},
vite:config write: true,
vite:config emptyOutDir: null,
vite:config manifest: false,
vite:config lib: false,
vite:config ssr: false,
vite:config ssrManifest: false,
vite:config brotliSize: true,
vite:config chunkSizeWarningLimit: 500,
vite:config watch: null
vite:config },
vite:config env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
vite:config assetsInclude: [Function: assetsInclude],
vite:config logger: {
vite:config hasWarned: false,
vite:config info: [Function: info],
vite:config warn: [Function: warn],
vite:config warnOnce: [Function: warnOnce],
vite:config error: [Function: error],
vite:config clearScreen: [Function: clearScreen],
vite:config hasErrorLogged: [Function: hasErrorLogged]
vite:config },
vite:config createResolver: [Function: createResolver],
vite:config optimizeDeps: { esbuildOptions: { keepNames: undefined } }
vite:config } +18ms
vite:deps Crawling dependencies using entries:
vite:deps C:/Users/Administrator/Desktop/code/Solution/front/index.html +0ms
vite:resolve 1ms /src/main.js -> C:/Users/Administrator/Desktop/code/Solution/front/src/main.js +0ms
vite:resolve 10ms vue -> D:/code/Solution/front/node_modules/vue/dist/vue.runtime.esm-bundler.js +26ms
vite:resolve 1ms ./App.vue -> C:/Users/Administrator/Desktop/code/Solution/front/src/App.vue +7ms
vite:resolve 3ms ./router -> C:/Users/Administrator/Desktop/code/Solution/front/src/router/index.js +5ms
vite:resolve 2ms ./store -> C:/Users/Administrator/Desktop/code/Solution/front/src/store/index.js +6ms
vite:resolve 11ms Vuex -> D:/code/Solution/front/node_modules/vuex/dist/vuex.esm-bundler.js +35ms
vite:resolve 12ms vue-router -> D:/code/Solution/front/node_modules/vue-router/dist/vue-router.esm-bundler.js +1ms
vite:resolve 0ms ../components/Home.vue -> C:/Users/Administrator/Desktop/code/Solution/front/src/components/Home.vue +6ms
vite:deps Scan completed in 205ms: {
vue: 'D:/code/Solution/front/node_modules/vue/dist/vue.runtime.esm-bundler.js',
Vuex: 'D:/code/Solution/front/node_modules/vuex/dist/vuex.esm-bundler.js',
'vue-router': 'D:/code/Solution/front/node_modules/vue-router/dist/vue-router.esm-bundler.js'
} +145ms
Pre-bundling dependencies:
vue
Vuex
vue-router
(this will be run only when your dependencies or config have changed)
> dep:Vuex:1:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vuex/dist/vuex.esm-bundler.js"
1 │ import d from "./D:/code/Solution/front/node_modules/vuex/dist/vuex.esm-bundler.js";export default d;
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> dep:vue:2:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vue/dist/vue.runtime.esm-bundler.js"
2 │ export * from "./D:/code/Solution/front/node_modules/vue/dist/vue.runtime.esm-bundler.js"
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> dep:vue-router:2:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vue-router/dist/vue-router.esm-bundler.js"
2 │ export * from "./D:/code/Solution/front/node_modules/vue-router/dist/vue-router.esm-bundler.js"
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error when starting dev server:
Error: Build failed with 3 errors:
dep:Vuex:1:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vuex/dist/vuex.esm-bundler.js"
dep:vue:2:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vue/dist/vue.runtime.esm-bundler.js"
dep:vue-router:2:14: error: Could not resolve "./D:/code/Solution/front/node_modules/vue-router/dist/vue-router.esm-bundler.js"
at failureErrorWithLog (C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:1449:15)
at C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:1131:28
at runOnEndCallbacks (C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:921:63)
at buildResponseToResult (C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:1129:7)
at C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:1236:14
at C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:609:9
at handleIncomingPacket (C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:706:9)
at Socket.readFromStdout (C:\Users\Administrator\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild\lib\main.js:576:7)
at Socket.emit (events.js:400:28)
at Socket.emit (domain.js:470:12)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 https://github.com/vuejs/vue-next 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.
Reactions are currently unavailable