Repository navigation
Commit 363d925
test(desktop): make the fake Tauri CLI write through the producer path
The fake CLI resolved frontendDist against the config directory and then both
wrote and read variant.txt there, so it agreed with itself no matter where the
wrapper pointed frontendDist. Repointing the production override at
<relative>/wrong-subdir still passed all three cases.
Write through BUZZ_PROTECTED_BUILD_OUTPUT -- the absolute path the wrapper
publishes for build-protected-feature-artifacts.mjs -- and keep the read on the
config-resolved consumer path. The two only agree when the wrapper's relative
frontendDist actually reaches the directory the build wrote to.
Verified on this branch:
- Unmodified wrapper: 3/3 pass.
- frontendDist -> <relative>/wrong-subdir: 0/3 with this change, 3/3 without it.
- Absolute-path regression restored: the relative/non-URL case still fails on
the value it is meant to catch.
- Desktop suite: 5843/5844. useDocumentVisible "focused polling pauses on blur"
fails about 1 run in 3 in isolation; both of its files are byte-identical to
the pre-PR commit, so it is unrelated.
- biome check clean.
Reported by Brain on behalf of wesbillman in review of #7177.
Signed-off-by: Jeff Hedlund <[email protected]>
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>1 parent 1f80098 commit 363d925
1 file changed
Lines changed: 6 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
29 | | - | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
30 | 34 | | |
31 | 35 | | |
32 | 36 | | |
| |||
0 commit comments