|
6 | 6 |
|
7 | 7 | # shellcheck disable=SC2154 |
8 | 8 | case "$Dependency" in |
9 | | - "Microsoft/VSCode") |
10 | | - # Always use `out/` (dev tsc) as the input tree, NOT `out-build/` |
11 | | - # (gulp release tree). |
12 | | - # |
13 | | - # `out-build/` carries the upstream-mangled bytes (`$Hp`, `$ZXb`, |
14 | | - # `$4e`, ...) but is missing every gulp-only artefact: the |
15 | | - # workbench bundler entries (`workbench.web.main.js`, |
16 | | - # `workbench.web.main.internal.js`, `workbench.desktop.main.js`) |
17 | | - # never reach `out-build/` because gulp emits them through a |
18 | | - # separate AMD-optimiser step Output does not run. Mixing the |
19 | | - # two trees produces an incoherent shipped artefact: Output's |
20 | | - # release `Target/Microsoft/VSCode/vs/code/electron-browser/ |
21 | | - # workbench/workbench.js` is mangled, but the supplement-copied |
22 | | - # siblings from `out/` are unmangled, and every cross-tree |
23 | | - # `import { $Hp } from './telemetry.js'` blows up at runtime |
24 | | - # because the unmangled file does not export `$Hp`. |
25 | | - # |
26 | | - # `out/` is unmangled but COMPLETE - every file VS Code's source |
27 | | - # tree references is present. Output's transforms operate on |
28 | | - # readable identifiers; consumers (Sky's Static/Application copy |
29 | | - # AND Sky's bundled Vite walk) see a single self-consistent |
30 | | - # universe of bytes; Vite/Rollup re-mangles for the bundled |
31 | | - # profile, browsers gzip the unbundled profile. The shipped |
32 | | - # artefact is a few hundred KB larger but works in every profile |
33 | | - # without the mangling-truth class of patches the previous |
34 | | - # `out-build/` path required. |
35 | | - Build="out" |
36 | | - ;; |
| 9 | +"Microsoft/VSCode") |
| 10 | + # Always use `out/` (dev tsc) as the input tree, NOT `out-build/` |
| 11 | + # (gulp release tree). |
| 12 | + # |
| 13 | + # `out-build/` carries the upstream-mangled bytes (`$Hp`, `$ZXb`, |
| 14 | + # `$4e`, ...) but is missing every gulp-only artefact: the |
| 15 | + # workbench bundler entries (`workbench.web.main.js`, |
| 16 | + # `workbench.web.main.internal.js`, `workbench.desktop.main.js`) |
| 17 | + # never reach `out-build/` because gulp emits them through a |
| 18 | + # separate AMD-optimiser step Output does not run. Mixing the |
| 19 | + # two trees produces an incoherent shipped artefact: Output's |
| 20 | + # release `Target/Microsoft/VSCode/vs/code/electron-browser/ |
| 21 | + # workbench/workbench.js` is mangled, but the supplement-copied |
| 22 | + # siblings from `out/` are unmangled, and every cross-tree |
| 23 | + # `import { $Hp } from './telemetry.js'` blows up at runtime |
| 24 | + # because the unmangled file does not export `$Hp`. |
| 25 | + # |
| 26 | + # `out/` is unmangled but COMPLETE - every file VS Code's source |
| 27 | + # tree references is present. Output's transforms operate on |
| 28 | + # readable identifiers; consumers (Sky's Static/Application copy |
| 29 | + # AND Sky's bundled Vite walk) see a single self-consistent |
| 30 | + # universe of bytes; Vite/Rollup re-mangles for the bundled |
| 31 | + # profile, browsers gzip the unbundled profile. The shipped |
| 32 | + # artefact is a few hundred KB larger but works in every profile |
| 33 | + # without the mangling-truth class of patches the previous |
| 34 | + # `out-build/` path required. |
| 35 | + Build="out" |
| 36 | + ;; |
37 | 37 |
|
38 | | - "CodeEditorLand/Editor") |
39 | | - Build="Source" |
40 | | - ;; |
| 38 | +"CodeEditorLand/Editor") |
| 39 | + Build="Source" |
| 40 | + ;; |
41 | 41 |
|
42 | | - *) |
43 | | - exit 1 |
44 | | - ;; |
| 42 | +*) |
| 43 | + exit 1 |
| 44 | + ;; |
45 | 45 | esac |
46 | 46 |
|
47 | 47 | Build "Source/**/*.{ts,json}" \ |
|
0 commit comments