`?no-inline` is included in asset url

[hi-ogawa]

Describe the bug

This looks a little unexpected since ?no-inline should work as a special marker and it's more like a shorthand for assetsInlineLimit config.

Reproduction

https://stackblitz.com/edit/vitejs-vite-a5dagvor?file=src%2Fmain.js

Steps to reproduce

• open stackblitz
• npm run dev shows /src/test.txt?no-inline
• npm run build && npm run preview shows /assets/test-iglrS_ky.txt?no-inline

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: 6.2.0-beta.1 => 6.2.0-beta.1

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 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.

[OnlyWick]

This may be intentional behavior.

vite/playground/assets/__tests__/assets.spec.ts

Lines 473 to 479 in 07091a1

	test('?no-inline svg import', async () => {
	expect(await page.textContent('.no-inline-svg')).toMatch(
	isBuild
	? /\/foo\/bar\/assets\/fragment-[-\w]{8}\.svg\?no-inline/
	: '/foo/bar/nested/fragment.svg?no-inline',
	)
	})

[OnlyWick]

I think we should keep this flag in the development environment and remove '?no-inline' in the production environment.