Inconsistent Metadata errors #7685

acidjazz · 2022-04-12T04:07:01Z

Describe the bug

I get this when starting my dev server

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:

    node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
      6 │ ...eactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
        ╵                                                                 ~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:vue:2:14:
      2 │ export * from "./node_modules/vue/dist/vue.runtime.esm-bundler.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an "onResolve" callback. All metadata provided for the same path must be consistent to ensure deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for a given path, so providing inconsistent metadata for the same path can cause non-determinism.

Possible duplicate of #7683

Reproduction

https://stackblitz.com/edit/vitejs-vite-f48pac?file=package.json

System Info

System:
    OS: macOS 12.0.1
    CPU: (8) arm64 Apple M1
    Memory: 95.61 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.volta/tools/image/node/16.13.1/bin/node
    Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
    npm: 8.6.0 - ~/.volta/tools/image/npm/8.6.0/bin/npm
  Browsers:
    Chrome: 100.0.4896.75
    Safari: 15.1
  npmPackages:
    @vitejs/plugin-vue: ^2.3.1 => 2.3.1
    vite: ^2.9.1 => 2.9.1

Used Package Manager

yarn

Logs

vite:resolve 0.31ms @vue/runtime-dom -> /Users/k/fume/tailvue/node_modules/@vue/runtime-dom/dist/runtime-dom.esm-bundler.js +0ms
  vite:resolve 0.41ms vue -> /Users/k/fume/tailvue/node_modules/vue/dist/vue.runtime.esm-bundler.js +3ms
✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:

    node_modules/@iconify/vue/dist/iconify.mjs:1:35:
      1 │ import { h, defineComponent } from 'vue';
        ╵                                    ~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:vue:2:14:
      2 │ export * from "../node_modules/vue/dist/vue.runtime.esm-bundler.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

  vite:resolve 0.33ms @vue/runtime-core -> /Users/k/fume/tailvue/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js +1ms
  vite:resolve 0.27ms @vue/shared -> /Users/k/fume/tailvue/node_modules/@vue/shared/dist/shared.esm-bundler.js +0ms
  vite:resolve 0.39ms @vue/reactivity -> /Users/k/fume/tailvue/node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js +10ms
11:03:58 PM [vite] error while updating dependencies:
Error: Build failed with 1 error:

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/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.

The text was updated successfully, but these errors were encountered:

AltStuff · 2022-04-12T04:10:17Z

Happens with React JS and React TS as well

$ vite

  vite v2.9.1 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 271ms.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

    node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20:
      16 │ var React = require('react');
         ╵                     ~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:react:1:23:
      1 │ export default require("./node_modules/react/index.js");
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

    node_modules/react-dom/cjs/react-dom.development.js:16:20:
      16 │ var React = require('react');
         ╵                     ~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:react:1:23:
      1 │ export default require("./node_modules/react/index.js");
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

10:49:37 PM [vite] error while updating dependencies:
Error: Build failed with 2 errors:
node_modules/react-dom/cjs/react-dom.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsi    at failureErrorWithLog (D:\projects\web-projects\test\node_modules\esbuild\lib\main.js:1603:15)
    at D:\projects\web-projects\test\node_modules\esbuild\lib\main.js:1249:28
    at runOnEndCallbacks (D:\projects\web-projects\test\node_modules\esbuild\lib\main.js:1034:63)
    at buildResponseToResult (D:\projects\web-projects\test\node_modules\esbuild\lib\main.js:1247:7)
    at D:\projects\web-projects\test\node_modules\esbuild\lib\main.js:666:9
    at Socket.readFromStdout (D:\projects\web-projects\test\node_modules\esbuild\lib\main.js:632:7)
    at Socket.emit (events.js:321:20)
    at addChunk (_stream_readable.js:294:12)

nathanoffline · 2022-04-12T04:12:46Z

was just going to file an issue
also tested with React & React TS

> test-vite@0.0.0 dev
> vite

  vite v2.9.1 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 234ms.

X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

    node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20:
      16 │ var React = require('react');
         ╵                     ~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:react:1:23:
      1 │ export default require("./node_modules/react/index.js");
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:
  
   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

    node_modules/react-dom/cjs/react-dom.development.js:16:20:
      16 │ var React = require('react');
         ╵                     ~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:react:1:23:
      1 │ export default require("./node_modules/react/index.js");
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

9:11:00 PM [vite] error while updating dependencies:
Error: Build failed with 2 errors:
node_modules/react-dom/cjs/react-dom.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
    at failureErrorWithLog (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1603:15)
    at C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1249:28
    at runOnEndCallbacks (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1034:63)
    at buildResponseToResult (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1247:7)
    at C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1356:14
    at C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:666:9
    at handleIncomingPacket (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:763:9)
    at Socket.readFromStdout (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:632:7)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)

qw789 · 2022-04-12T04:26:25Z

Happens with VUE JS as well
`
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
╵ ~~~~~

The original metadata for that path comes from when it was imported here:

dep:vue:2:14:
  2 │ export * from "./node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js"
    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:

{

"pluginName": null,

"pluginName": "vite:dep-pre-bundle",
}

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
"onResolve" callback. All metadata provided for the same path must be consistent to ensure
deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
a given path, so providing inconsistent metadata for the same path can cause non-determinism.

下午12:21:14 [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:
at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28
at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63)
at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9
at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9)
at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7)
at Socket.emit (node:events:390:28)
at addChunk (node:internal/streams/readable:315:12)
Vite Error, /node_modules/.vite/deps/vue-router.js?v=18f23ae8 optimized info should be defined
X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:

node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
  6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue'; 
    ╵                                                                                                                                                             ~~~~~

The original metadata for that path comes from when it was imported here:

dep:vue:2:14:
  2 │ export * from "./node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js"
    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:

{

"pluginName": null,

"pluginName": "vite:dep-pre-bundle",
}

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
"onResolve" callback. All metadata provided for the same path must be consistent to ensure
deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
a given path, so providing inconsistent metadata for the same path can cause non-determinism.

下午12:21:19 [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:
at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28
at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63)
at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9
at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9)
at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7)
at Socket.emit (node:events:390:28)
at addChunk (node:internal/streams/readable:315:12)
`

ismoiliy98 · 2022-04-12T04:35:16Z

Happens with preact as well

Logs

❯ yarn dev
yarn run v1.22.17
$ vite

  vite v2.9.1 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 389ms.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:

    node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:38:
      1 │ import{options as r,Fragment as _}from"preact";export{Fragment}from"preact";var o=0;function e(_,e,n,t,f){var l,s,u={};for(s in e)"ref"==s?l=e[s]:u...
        ╵                                       ~~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:preact:2:14:
      2 │ export * from "./node_modules/preact/dist/preact.module.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:
  
   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }
  
  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:

    node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:67:
      1 │ import{options as r,Fragment as _}from"preact";export{Fragment}from"preact";var o=0;function e(_,e,n,t,f){var l,s,u={};for(s in e)"ref"==s?l=e[s]:u...
        ╵                                                                    ~~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:preact:2:14:
      2 │ export * from "./node_modules/preact/dist/preact.module.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:
  
   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }
  
  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

9:23:20 AM [vite] error while updating dependencies:
Error: Build failed with 2 errors:
node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:38: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:
node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:67: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:
    at failureErrorWithLog (/preact-project/node_modules/esbuild/lib/main.js:1603:15)
    at /preact-project/node_modules/esbuild/lib/main.js:1249:28
    at runOnEndCallbacks (/preact-project/node_modules/esbuild/lib/main.js:1034:63)
    at buildResponseToResult (/preact-project/node_modules/esbuild/lib/main.js:1247:7)
    at /preact-project/node_modules/esbuild/lib/main.js:1356:14
    at /preact-project/node_modules/esbuild/lib/main.js:666:9
    at handleIncomingPacket (/preact-project/node_modules/esbuild/lib/main.js:763:9)
    at Socket.readFromStdout (/preact-project/node_modules/esbuild/lib/main.js:632:7)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)

Jhonatan-1504 · 2022-04-12T04:39:23Z

i use another version in vue-router is result for me, in react sorry i dont know

i think, this error is in the vite compilation, i have another project with this version vue:

it works normally but when i create a new project it throws the error

qw789 · 2022-04-12T04:53:23Z

i use another version in vue-router is result for me, in react sorry i dont know

i think, this error is in the vite compilation, i have another project with this version vue:

it works normally but when i create a new project it throws the error

you delete the node_modules,reinstall then try it

abramsotocinal · 2022-04-12T04:56:59Z

Same error here

Using vue3-latest

I literally just now uninstalled vue-router and downgraded to v3 of router and works. This is a fresh install btw so i can't tell yet how this will behave

Happens with VUE JS as well ` node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: 6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue'; ╵ ~~~~~

The original metadata for that path comes from when it was imported here:
dep:vue:2:14:
  2 │ export * from "./node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js"
    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The difference in metadata is displayed below:

{
* "pluginName": null,


* "pluginName": "vite:dep-pre-bundle",
  }
This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an "onResolve" callback. All metadata provided for the same path must be consistent to ensure deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for a given path, so providing inconsistent metadata for the same path can cause non-determinism.

下午12:21:14 [vite] error while updating dependencies: Error: Build failed with 1 error: node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here: at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28 at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63) at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14 at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9 at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9) at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7) at Socket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:315:12) Vite Error, /node_modules/.vite/deps/vue-router.js?v=18f23ae8 optimized info should be defined X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
  6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue'; 
    ╵                                                                                                                                                             ~~~~~  
The original metadata for that path comes from when it was imported here:
dep:vue:2:14:
  2 │ export * from "./node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js"
    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The difference in metadata is displayed below:

{
* "pluginName": null,


* "pluginName": "vite:dep-pre-bundle",
  }
This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an "onResolve" callback. All metadata provided for the same path must be consistent to ensure deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for a given path, so providing inconsistent metadata for the same path can cause non-determinism.

下午12:21:19 [vite] error while updating dependencies: Error: Build failed with 1 error: node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/.pnpm/vue@3.2.31/node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here: at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28 at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63) at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14 at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9 at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9) at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7) at Socket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:315:12) `

ismoiliy98 · 2022-04-12T05:02:14Z

The issue seems related to esbuild

A temporary workaround is to add resolution to your package.json:

"resolutions": {
  "esbuild": "0.14.34"
}

jifakir · 2022-04-12T05:04:02Z

Same to me on react
$ vite

vite v2.9.1 dev server running at:

Local: http://localhost:3000/
Network: use --host to expose

ready in 414ms.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20:
  16 │ var React = require('react');
     ╵                     ~~~~~~~

The original metadata for that path comes from when it was imported here:

dep:react:1:23:
  1 │ export default require("./node_modules/react/index.js");
    ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:

{

"pluginName": null,

"pluginName": "vite:dep-pre-bundle",
}

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
"onResolve" callback. All metadata provided for the same path must be consistent to ensure
deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
a given path, so providing inconsistent metadata for the same path can cause non-determinism.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

node_modules/react-dom/cjs/react-dom.development.js:16:20:
  16 │ var React = require('react');
     ╵                     ~~~~~~~

The original metadata for that path comes from when it was imported here:

dep:react:1:23:
  1 │ export default require("./node_modules/react/index.js");
    ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:

{

"pluginName": null,

"pluginName": "vite:dep-pre-bundle",
}

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
"onResolve" callback. All metadata provided for the same path must be consistent to ensure
deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
a given path, so providing inconsistent metadata for the same path can cause non-determinism.

10:57:04 AM [vite] error while updating dependencies:
Error: Build failed with 2 errors:
node_modules/react-dom/cjs/react-dom.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
at failureErrorWithLog (/run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:1603:15)
at /run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:1249:28
at runOnEndCallbacks (/run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:1034:63)
at buildResponseToResult (/run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:1247:7)
at /run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:1356:14
at /run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:666:9
at handleIncomingPacket (/run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:763:9)
at Socket.readFromStdout (/run/media/fakir/Store/Code/Project/gsap-parallex/node_modules/esbuild/lib/main.js:632:7)
at Socket.emit (node:events:520:28)
at addChunk (node:internal/streams/readable:315:12)

qw789 · 2022-04-12T05:04:43Z

thanks,that is useful

dsrkafuu · 2022-04-12T05:04:54Z

Same issue here.
PM: pnpm
Vite: 2.9.1

@Geebrox's temporary workaround works well.

The issue seems related to esbuild

A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

East333 · 2022-04-12T05:08:12Z

I hava the same error, when the version is

"vue": "3.2.26",
"vue-router": "4.0.12",
"@vitejs/plugin-vue": "1.9.4",
"@vue/compiler-sfc": "3.2.22",
"vite": "2.6.14",

things are ok,no error.
But when the version is

"vue": "3.2.31",  
"vue-router": "4.0.12",
"@vitejs/plugin-vue": "2.2.4",
"@vue/compiler-sfc": "3.2.31",
"vite": "2.8.6",

the version of vite is 2.8.6 or 2.9.1 , same error

nathanoffline · 2022-04-12T05:12:54Z

Unfortunately, I'm unable to replicate @Geebrox's solution... are resolutions PNPM specific?

jifakir · 2022-04-12T05:15:17Z

The issue seems related to esbuild

A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

Working on Reactjs too, Thanks man!

East333 · 2022-04-12T05:17:51Z

Unfortunately, I'm unable to replicate @Geebrox's solution... are resolutions PNPM specific?

maybe is yarn

bluwy · 2022-04-12T05:20:01Z

This looks like a duplicate of #7683 as noted in the issue description. Closing to keep discussion in one place.

abramsotocinal · 2022-04-12T05:20:58Z

Thank you, works.

Also, i'm using npm not yarn so if anyone comes here using npm, fyi its equivalent is overrides

"overrides": {
    "esbuild": "0.14.34"
  },

The issue seems related to esbuild

A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

Abeiv · 2022-04-12T06:21:58Z

The issue seems related to esbuild

A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

Thank man 👍！

songyu641660583 · 2022-04-12T07:14:49Z

请问解决这个问题了吗，我也是这个问题 vue项目

Abeiv · 2022-04-12T07:20:29Z

请问解决这个问题了吗，我也是这个问题 vue项目

解决了，删除 node_modules 重新install一下就行了

songyu641660583 · 2022-04-12T07:21:46Z

Abeiv

谢谢呢
"resolutions": {
"esbuild": "0.14.34"
}
这个方法很好，虽然不知道为什么

patak-dev · 2022-04-12T07:26:42Z

Please remove the custom resolutions, esbuild 0.14.36 has been released reverting the problematic change

East333 · 2022-04-12T07:30:13Z

Abeiv

谢谢呢 "resolutions": { "esbuild": "0.14.34" } 这个方法很好，虽然不知道为什么

原因是vite的依赖包esbuild今天上午发布了一个新版本0.14.35，有问题。0.14.34是没问题的。简单来说，resolutions是yarn的固定版本的一个方法。刚刚，esbuild又发布了一个新版本0.14.36，解决了这个问题

vL1n · 2022-04-12T10:08:14Z

The issue seems related to esbuild

A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

that's useful for me.

acidjazz added the pending triage label Apr 12, 2022

sapphi-red mentioned this issue Apr 12, 2022

metadata returned by plugin is inconsistent happens evanw/esbuild#2177

Closed

bluwy closed this as completed Apr 12, 2022

nathanoffline mentioned this issue Apr 12, 2022

esbuild0.14.35 is not compate with vite #7683

Closed

7 tasks

github-actions bot locked and limited conversation to collaborators Apr 27, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Inconsistent Metadata errors #7685

Inconsistent Metadata errors #7685

acidjazz commented Apr 12, 2022

AltStuff commented Apr 12, 2022 •

edited

Loading

nathanoffline commented Apr 12, 2022 •

edited

Loading

qw789 commented Apr 12, 2022 •

edited

Loading

ismoiliy98 commented Apr 12, 2022

Jhonatan-1504 commented Apr 12, 2022

qw789 commented Apr 12, 2022

abramsotocinal commented Apr 12, 2022 •

edited

Loading

ismoiliy98 commented Apr 12, 2022

jifakir commented Apr 12, 2022

qw789 commented Apr 12, 2022

dsrkafuu commented Apr 12, 2022

East333 commented Apr 12, 2022

nathanoffline commented Apr 12, 2022

jifakir commented Apr 12, 2022

East333 commented Apr 12, 2022

bluwy commented Apr 12, 2022

abramsotocinal commented Apr 12, 2022

Abeiv commented Apr 12, 2022

songyu641660583 commented Apr 12, 2022

Abeiv commented Apr 12, 2022

songyu641660583 commented Apr 12, 2022

patak-dev commented Apr 12, 2022

East333 commented Apr 12, 2022

vL1n commented Apr 12, 2022

Inconsistent Metadata errors #7685

Inconsistent Metadata errors #7685

Comments

acidjazz commented Apr 12, 2022

Describe the bug

Reproduction

System Info

Used Package Manager

Logs

Validations

AltStuff commented Apr 12, 2022 • edited Loading

nathanoffline commented Apr 12, 2022 • edited Loading

qw789 commented Apr 12, 2022 • edited Loading

ismoiliy98 commented Apr 12, 2022

Jhonatan-1504 commented Apr 12, 2022

qw789 commented Apr 12, 2022

abramsotocinal commented Apr 12, 2022 • edited Loading

ismoiliy98 commented Apr 12, 2022

jifakir commented Apr 12, 2022

qw789 commented Apr 12, 2022

dsrkafuu commented Apr 12, 2022

East333 commented Apr 12, 2022

nathanoffline commented Apr 12, 2022

jifakir commented Apr 12, 2022

East333 commented Apr 12, 2022

bluwy commented Apr 12, 2022

abramsotocinal commented Apr 12, 2022

Abeiv commented Apr 12, 2022

songyu641660583 commented Apr 12, 2022

Abeiv commented Apr 12, 2022

songyu641660583 commented Apr 12, 2022

patak-dev commented Apr 12, 2022

East333 commented Apr 12, 2022

vL1n commented Apr 12, 2022

AltStuff commented Apr 12, 2022 •

edited

Loading

nathanoffline commented Apr 12, 2022 •

edited

Loading

qw789 commented Apr 12, 2022 •

edited

Loading

abramsotocinal commented Apr 12, 2022 •

edited

Loading