fix: don't strip base from imports

[sapphi-red]

import analysis plugin was rewriting from import '/home/path/to/file.js' to import '/path/to/file.js' when the base is /home/. But since we treat the ids in imports as file paths instead of URLs, we shouldn't trim the base here. (import analysis plugin rewrites file paths into URLs)

fixes vitejs/vite-plugin-vue#25
close #7224

[sapphi-red]

/ecosystem-ci run

[pkg-pr-new]

Open in StackBlitz

pnpm add https://pkg.pr.new/vitejs/vite/@vitejs/plugin-legacy@21221

npm i https://pkg.pr.new/vitejs/vite/@vitejs/plugin-legacy@21221

yarn add https://pkg.pr.new/vitejs/vite/@vitejs/plugin-legacy@21221.tgz

pnpm add https://pkg.pr.new/vitejs/vite@21221

npm i https://pkg.pr.new/vitejs/vite@21221

yarn add https://pkg.pr.new/vitejs/vite@21221.tgz

commit: 42e2572

[vite-ecosystem-ci]

📝 Ran ecosystem CI on f1d979b: Open

suite	result	latest scheduled
histoire	❌ failure	✅ success
nuxt	❌ failure	✅ success
astro	❌ failure	❌ failure
analogjs	✅ success	❌ failure
one	❌ failure	✅ success
qwik	❌ failure	❌ failure
rakkas	❌ failure	✅ success
react-router	❌ failure	⏹️ cancelled
sveltekit	❌ failure	✅ success
unocss	✅ success	❌ failure
storybook	❌ failure	✅ success
vike	❌ failure	❌ failure
vite-plugin-cloudflare	❌ failure	❌ failure
vite-plugin-pwa	❌ failure	✅ success
vite-plugin-svelte	❌ failure	✅ success
vitest	❌ failure	✅ success

✅ ladle, marko, laravel, quasar, vite-plugin-vue, vite-environment-examples, vite-setup-catalogue, vuepress, vitepress, waku, vite-plugin-rsc, vite-plugin-react

[sapphi-red]

probably better to make a PR to v7 branch and then run the ecosystem-ci
also need to add tests

[sapphi-red]

It seems to be safe: #21241

[sapphi-red]

ok, failing properly