vite

Describe the bug For string interpolation with valid expression, dollar sign concat with string happen to be invalid expression. In dev server , this runs correctly, renders expression, and string . however succeeds, without producing any javascript output, no In my tests, below will not trigger the problem: 1. valid object 2. escape dollar 2. only dollar without first valid expression Reproduction https://stackblitz.com/edit/vitejs-vite-xhnudkqg?file=src%2FApp.tsx&terminal=dev Steps to reproduce Use stackblitz, new terminal, run System Info Used Package Manager npm Logs Click to expand! Validations [x] Follow our Code of Conduct [x] Read the Contributing Guidelines. [x] Read the docs. [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [x] 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. [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [x] The provided reproduction is a minimal reproducible example of the bug.

Describe the bug in decides where hoisted statements may be inserted by matching the hashbang with: In a JavaScript regex, matches no line terminator — including . So for a module whose first line ends in CRLF (), stops before the , the required can't match, and the regex fails as a whole: then returns , and ( — ) hoists the statements to position 0, above the hashbang, stranding in the middle of the module: A hashbang is only legal at offset 0, so V8 rejects the module with a bare — no file position, no code frame — which makes the failure very hard to attribute. With LF endings the regex matches and imports are hoisted after the shebang, as intended. That behavior was fixed for LF in #12976 by #12985 (the PR that introduced ); the CRLF case was left behind. Code (v8.0.16): https://github.com/vitejs/vite/blob/v8.0.16/packages/vite/src/node/utils.ts#L1830-L1835 https://github.com/vitejs/vite/blob/v8.0.16/packages/vite/src/node/ssr/ssrTransform.ts#L94-L95 Still present on (791843e1591e): https://github.com/vitejs/vite/blob/791843e1591e/packages/vite/src/node/utils.ts#L1992-L1997 is also used by to anchor hoisted assignments (https://github.com/vitejs/vite/blob/791843e1591e/packages/vite/src/node/plugins/importAnalysis.ts#L993), so any consumer mis-anchors on CRLF hashbang files; the practical hit is the SSR / module-runner path. Practical impact: a Vitest test importing a shebang'd CLI entry passes on Linux CI but fails to collect on a Windows checkout with (repo stores LF, working tree gets CRLF). Likely earlier sighting of this exact variant: vitest-dev/vitest#3244 — Windows paths in the log, filed right as Vite 4.3's import hoisting shipped, closed as a duplicate of #12976, but the LF-only fix in #12985 would not have helped a CRLF checkout. Suggested fix: accept an optional (and, while at it, a hashbang line with no trailing newline): Or, to follow the ECMAScript HashbangComment grammar exactly (the comment runs to any LineTerminator: , , , ), something like . Either way the insertion point must land after the full terminator sequence — after the of a pair, never between and . Reproduction https://github.com/laurentminguez/vite-crlf-hashbang-repro → . The repro commits with byte-exact CRLF (marked in ) and re-asserts the bytes in a step, so it reproduces on any OS — including StackBlitz: https://stackblitz.com/github/laurentminguez/vite-crlf-hashbang-repro (run in the terminal). A fully scripted equivalent is below. Steps to reproduce Self-contained — the script writes the CRLF bytes explicitly, so it reproduces on any OS; no git or involvement needed: How this is hit in real projects: a shebang'd CLI entry is stored with LF in git and checked out on Windows with , so the working-tree file has CRLF — the module then fails to import under vitest / vite-node / the module runner on that machine only, while Linux CI stays green. Workaround until fixed: force LF via (e.g. ). System Info Used Package Manager npm Logs CRLF run: LF control run (only line endings changed): Validations [x] Follow our Code of Conduct [x] Read the Contributing Guidelines. [x] Read the docs. [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [x] Make sure this is a Vite issue and not a framework-specific issue. [x] Check that this is a concrete bug. [x] The provided reproduction is a minimal reproducible example of the bug.