pre-bundle question when import path is absolute path

Here is the example code:

// Area.tsx
import { areaList } from '@vant/area-data';
export default () => {
  console.log(areaList)
  return <div>this is arrea</div>
}

1.Pre-bundle will miss @vant/area-data:

// App.tsx
import Area from '/Users/3lang/Workspace/demo/vite-markdown/src/Area.tsx'

2.Pre-bundle as expected

// App.tsx
import Area from '/Users/3lang/Workspace/demo/vite-markdown/src/Area'

Vite resolved resource path resolvedId consistent with the rawid (user import code). Vite will be ignored as a virtual resource, and pre bunlde will not contain this Dep https://github.com/vitejs/vite/blob/cf03ecf3daf1f00c81de07b2429d38919ec920e7/packages/vite/src/node/optimizer/scan.ts#L511-L514

However, if it is a Vue (svelte) project, this will not happen

It will be dealt with internally: https://github.com/vitejs/vite/blob/cf03ecf3daf1f00c81de07b2429d38919ec920e7/packages/vite/src/node/optimizer/scan.ts#L268-L278

[3lang3]

The absolute path code was generated by the CLI tool, and then the pre bundle did not run as expected, which made me very confused. Therefore, I debugged the code and found the logic of resolvedid = = = rawid, so I created this issue.

Yes, I modify my cli code to adaptation vite with an alias

[bluwy]

That might not be correct for this issue’s instance, but following #5494, I don’t think Vite has ever supported importing absolute paths, hence the quirk.

I also don’t quite understand the point of the vue/svelte code linked, I don’t think that affects this issue. That part of the code makes sure that Vite’s scanner doesn’t have conflicting var names when parsing vue/svelte files to JS.

Nonetheless, I think the correct way forward is to avoid absolute paths, and use aliases if possible.