Dynamic import fails even if following all rules outlined in Rollup limitations doc

[brunobely]

Describe the bug

I'm trying to dynamically import files with the format \./${import.meta.env.VITE_PROJECT_NAME}__site_config.json``, however I get a warning saying Vite cannot statically analyze the import. I'm following all the rules outlined in Rollup dynamic import limitations doc.

If I change the the static portion of the string to be at the beginning of the path, however, like \./site_config__${import.meta.env.VITE_PROJECT_NAME}.json``, it works normally. Is there a reason for this?

Reproduction

https://stackblitz.com/edit/vitejs-vite-ma2hgh?file=main.js

System Info

System:
    OS: macOS 12.3.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 979.52 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.0.1 - ~/.nvm/versions/node/v17.0.1/bin/node
    npm: 8.10.0 - ~/.nvm/versions/node/v17.0.1/bin/npm
  Browsers:
    Brave Browser: 99.1.36.117
    Chrome: 102.0.5005.61
    Chrome Canary: 104.0.5095.0
    Firefox: 100.0
    Safari: 15.4

Used Package Manager

pnpm

Logs

1  |  import { SiteConfig } from "$proto/ts/common/config/site_config";
2  |  console.log(`dynamically importing ${import.meta.env.VITE_PROJECT_NAME}__site_config.json`);
3  |  const configJson = (await import(`./${import.meta.env.VITE_PROJECT_NAME}__site_config.json`)).default;
   |                                   ^
4  |  console.log(configJson);
5  |  export default SiteConfig.fromJson(configJson);
The above dynamic import cannot be analyzed by vite.
See https://github.com/rollup/plugins/tree/master/packages/dynamic-import-vars#limitations for supported dynamic import formats. If this is intended to be left as-is, you can use the /* @vite-ignore */ comment inside the import() call to suppress this warning.

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.

[sapphi-red]

Closing as it is fixed by #7756 which is released with Vite v3.0.0-alpha.0.

The reason was because this part was not accurate.

vite/packages/vite/src/node/plugins/importAnalysis.ts

Lines 712 to 715 in 5af8e76

	// must be more specific if importing from same dir
	if (url.startsWith('./${') && url.indexOf('/') === url.lastIndexOf('/')) {
	return false
	}