pack and install: should be able to webpack the library failed

[flaky-bot[bot]]

Note: #1636 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

---

commit: 422de68d8d9ea66e6bf1fea923f61c8af0842420 buildURL: Build Status, Sponge status: failed

[flaky-bot[bot]]

Looks like this issue is flaky. :worried:

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (422de68d8d9ea66e6bf1fea923f61c8af0842420), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[danielbankhead]

Very strange error:

<testsuite name="Mocha Tests" tests="2" failures="0" errors="2" skipped="0" timestamp="Sun, 28 Jan 2024 09:36:11 GMT" time="223.478">
<testcase classname="pack and install" name="should be able to use the d.ts" time="27.215">
<failure>Command failed with exit code 1: npm install Error: Command failed with exit code 1: npm install at makeError (node_modules/execa/lib/error.js:60:11) at handlePromise (node_modules/execa/index.js:118:26) at processTicksAndRejections (internal/process/task_queues.js:95:5) at null.packAndInstall (system-test/test.kitchen.ts:43:3) at Context.<anonymous> (system-test/test.kitchen.ts:56:5)</failure>
</testcase>
<testcase classname="pack and install" name="should be able to webpack the library" time="27.485">
<failure>Command failed with exit code 1: npm install Error: Command failed with exit code 1: npm install at makeError (node_modules/execa/lib/error.js:60:11) at handlePromise (node_modules/execa/index.js:118:26) at processTicksAndRejections (internal/process/task_queues.js:95:5) at null.packAndInstall (system-test/test.kitchen.ts:43:3) at Context.<anonymous> (system-test/test.kitchen.ts:62:5)</failure>
</testcase>
</testsuite>

However, the second build actually passed.