[vite] Failed to resolve module import "vue.js".

Describe the bug

I am struggling with this error for a whole day…

I cannot find vue.js module in devtools->Application->Feames->Scripts, but found vue.runtime.esm-bundler.js

Reproduction

Please provide a link to a repo that can reproduce the problem you ran into.

A reproduction is required unless you are absolutely sure that the the problem is obvious and the information you provided is enough for us to understand what the problem is. If a report has only vague description (e.g. just a generic error message) and has no reproduction, it will be closed immediately.

System Info

• required vite version: 1.0.0.rc.1
• required Operating System: macOS 10.15
• required Node version: 10.12
• Optional:
  • npm/yarn version
  • Installed vue version (from yarn.lock or package-lock.json)
  • Installed @vue/compiler-sfc version

Logs (Optional if provided reproduction)

[ais-one]

Reproduction Repo: https://github.com/Auxxxxlx/exampleG6

I got something new. If you delete vue in dependencies(package.json), like:

{
  "name": "etstt",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "vite build"
  },
  "dependencies": {},
  "devDependencies": {
    "@vue/compiler-sfc": "^3.0.0-rc.1",
    "vite": "^1.0.0-rc.1"
  }
}

Then you can start the app with no error.

But if you add vue in dependencies, like:

{
  "name": "etstt",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "vite build"
  },
  "dependencies": {
    "vue": "^3.0.0-rc.1"
  },
  "devDependencies": {
    "@vue/compiler-sfc": "^3.0.0-rc.1",
    "vite": "^1.0.0-rc.1"
  }
}

Then you will find the following error in console.

---

I got it to work… Please do the following…

1. npm update

2. vite.config.js - remove everything

module.exports = {
}

One last thing, ant design will not work… using imports as it requires webpack… Same for many other UI frameworks.

Web components work nicely though…

[yyx990803]

If you don’t know what optimizeDeps is doing, it’s best not to disable it… it’s required for some non-esm dependencies to work. But in the case of Vue resolving this is a bug.