Forth test

[oxe-i]

Files for a failing test to the Forth exercise, with a results.json (renamed as expected_results.json) and the files for the exercise.

[oxe-i]

@SleeplessByte as discussed in the forum

[oxe-i]

I believe the problem is in RegExp.escape

[SleeplessByte]

I believe the problem is in RegExp.escape

You're expectation is correct. This is not supported before Node 24.

The current LTS (long term support) is 22, which is what we support officially. That also means that we would expect this to fail for you using the CLI and not the browser (as discussed on the forum).

We can leave this PR open and merge it when LTS moves to 24, later this year:

[oxe-i]

That's a bit odd. My machine here says I'm using Node v.22.16 and, when I open the REPL and try RegExp.escape it gives me an error. However corepack pnpm test gives me a pass to all tests.

[oxe-i]

It seems there's an internal RegExp.escape implemented in a module inside core-js folder. When I check definition for the function in VSCode, it directs me to an internal interface in TypeScript that exists since ECMAScript 7. And when I check the folder for the exercise, there's a node_modules/.pnpm/core-js@3.42.0/node_modules/core-js/modules/es.regexp.escape.js with the actual code for the function:

It seems I inadvertently have fallen into quite a rabbit hole! What a coincidence!

[SleeplessByte]

Yeah, we use it when you run it locally! Check out https://github.com/exercism/babel-preset-javascript/blob/main/index.cjs#L11 which loads core-js during regular use.

I thought we set-up this test-runner to use the same, but it seems to not do that? Imma try out to update the test-runner, and then we can merge in that update here and see if that makes it work.

edit: yeah we do, but we were running 3.38 instead of 3.44

[SleeplessByte]

More data:

• Remove RegExp.escape zloirock/core-js#116 (it was removed in 2015)
• zloirock/core-js@ea68a15 (it was re-added in 3.33)
• zloirock/core-js@7321cc1 (it was moved to stable in 3.41)

We were running polyfill 3.38, but now that I bumped it to '3.44', it runs fine.

I generated results.json for your solution, so we can merge it.