Commit b357233
committed
fix: run rm.js from the package root, drop the ignored copySync arg
The conda-lock and extract scripts cd into a subdir first and then called
node scripts/rm.js, but that path only resolves from the repo root, so the
removal failed with a module-not-found once the cwd changed. npm and yarn
always start a run-script at the package root, so the natural fix is to do
the removal there against a root-relative target and let the later cd handle
only conda-lock and tar, which genuinely need the subdir. This avoids a
../scripts/rm.js form that would recouple the path to the cd depth.
copySync already hardcodes { recursive: true } in its definition, so the
third argument passed at the copy-extras call site was silently ignored;
removing it keeps the recursive copy and drops the misleading option.
Note: AI-assisted (Claude Code). Manually verified: rm.js from root cwd with
a subdir glob and a glob-miss both remove the right paths and exit 0;
copySync copies a nested tree; type-check, 443 unit tests and yarn build all
pass on the merged branch.1 parent fdfa121 commit b357233
2 files changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
34 | | - | |
| 33 | + | |
| 34 | + | |
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
40 | 40 | | |
41 | 41 | | |
42 | | - | |
| 42 | + | |
43 | 43 | | |
44 | 44 | | |
45 | 45 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
167 | 167 | | |
168 | 168 | | |
169 | 169 | | |
170 | | - | |
| 170 | + | |
171 | 171 | | |
172 | 172 | | |
173 | 173 | | |
| |||
0 commit comments