Error in spec for palindrome-products

[keiravillekode]

Described in
https://forum.exercism.org/t/error-in-spec-for-palindrome-products/16214

Reproduced:
Submitting the example solution gives

We received the following error when we ran your code:
  ● Test suite failed to run

    Cannot find module 'core-js/modules/es.array.push.js' from '../..<solution>/palindrome-products.spec.js'

Possible steps for investigation:

• Study https://github.com/exercism/wasm-test-runner/
• Add a ci workflow that calls wasm-test-runner, like Idris
• Generate a simpler palindrome-products.spec.js that resembles WASM specs not experiencing the problem.

[atk]

I can only infer from the outside what happened, so these are merely my assumptions: during deployment, the network connection became unstable, leading to the core package not being available. Since Array.prototype.push is the first polyfill to be called by Babel, the missing package leads to errors before the tests even run.

Proposed solution: redeployment with new version.

[atk]

I have changed the spec not to use Array.prototype.push, but I could only locally reproduce the issue by removing the file that was missing in the testing back end.

[keiravillekode]

The spec change has successfully fixed palindrome-products.

I think the error was a consequence of
https://github.com/exercism/wasm-test-runner/blob/07445f4d85366138321fc379f8b5f08127dd193c/Dockerfile#L32

Minimizing the test runner image size is important to save Exercism storage costs on the test runner servers. If we add to package.json or pnpm-lock.yaml, I'm not sure how we measure the increase in image size.

If we add a ci workflow that calls wasm-test-runner, the problem won't reach users again.

[atk]

If we wanted to minimize the bundle size for the test runner, we should consider switching to vitest. On the other hand, we could consider moving away from JS and run the code using wasmer.io