2.5.0-beta fails to works with resolve.alias

[ghost]

Describe the bug

Having resolve.alias breaks dev on Win10
(was working on 2.4.4)

Reproduction

https://github.com/web2033/vite-2.5.0-beta-bug

System Info

Win 10

Used Package Manager

npm

Logs

No response

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.

[ygj6]

Issues caused by upgrading @rollup/plugin-alias from 3.1.4 to 3.1.5，but I think vite has a problem with alias handling and I am fixing it.

[ghost]

This? rollup/plugins#896

[ygj6]

Yes, you can go back to @rollup/[email protected] The issue does not exist

@rollup/[email protected] keep the window drive letter

[ygj6]

Because @rollup/[email protected] will delete the window drive letter, D:\src will become \src，
but @rollup/[email protected] retains the window drive letter, so path.resolve(__dirname,'/src') this kind of wrong path is no longer supported, there is no issue with vite processing,
we need to pass the correct path path.resolve(__dirname,'src'), works normally.

[ghost]

That worked.
So starting from 2.5.0 I need to remove that extra /?

[patak-dev]

Good catch @ygj6, I hope this doesn't break others. I don't know if we can do much here.

[ygj6]

path.resolve(__dirname,'/src') is a wrong path, not the real project root path, so I don’t think Vite should do anything.