Commit 21e108e
ci: workaround npm/cli#4828 for Next build native bindings
The e2e-pr, visual-regression, and e2e-prod jobs build dojolm-web via
`next build`, which loads `next/font` and the @next/swc native binding.
CI intermittently fails with "Cannot find native binding" because npm
ci skips some platform-specific optional deps (upstream bug
npm/cli#4828). The tests job is unaffected because vitest was patched
separately to bypass PostCSS.
Add an `npm install --no-save` step after `npm ci` that explicitly
pulls the Linux x64 gnu bindings for @next/swc, lightningcss, and
@tailwindcss/oxide. `|| true` keeps the step non-blocking if a
package already resolved correctly. --no-save means the lockfile is
not touched.
Long-term fix: regenerate package-lock.json locally on Linux to
guarantee platform native deps are recorded, or switch CI to an
install pattern that handles optional deps reliably.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 912a091 commit 21e108e
1 file changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
280 | 280 | | |
281 | 281 | | |
282 | 282 | | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
283 | 286 | | |
284 | 287 | | |
285 | 288 | | |
| |||
294 | 297 | | |
295 | 298 | | |
296 | 299 | | |
297 | | - | |
| 300 | + | |
| 301 | + | |
298 | 302 | | |
299 | 303 | | |
300 | 304 | | |
| |||
316 | 320 | | |
317 | 321 | | |
318 | 322 | | |
| 323 | + | |
| 324 | + | |
| 325 | + | |
319 | 326 | | |
320 | 327 | | |
321 | 328 | | |
| |||
357 | 364 | | |
358 | 365 | | |
359 | 366 | | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
360 | 370 | | |
361 | 371 | | |
362 | 372 | | |
| |||
0 commit comments