'npm test' command hangs/doesn't exit

Hello, I’m having an issue executing tests in my terminal. When I type in npm test, the test will start to run, and then it never exits – it just hangs there. I have to keep canceling the test with ^C. After doing some googling this morning I uninstalled and reinstalled npm for node, updated yarn, jest, and homebrew.

However, none of these actions have solved my issue. I just want to be able to run my tests smoothly again and focus on learning instead of troubleshooting. Can anybody help me out?

Here is the full output on my terminal after running a test:

> exercism-javascript@2.1.0 test /Users/bobbychicano/Exercism/javascript/resistor-color-duo
> jest ./*

 FAIL  ./resistor-color-duo.spec.js
  Resistor Colors
    ✕ Brown and black (2 ms)
    ○ skipped Blue and grey
    ○ skipped Yellow and violet
    ○ skipped Orange and orange
    ○ skipped Ignore additional colors

  ● Resistor Colors › Brown and black

    Remove this statement and implement this function

      5 | 
      6 | export const decodedValue = () => {
    > 7 |   throw new Error("Remove this statement and implement this function");
        |         ^
      8 | };
      9 | 

      at decodedValue (resistor-color-duo.js:7:9)
      at Object.<anonymous> (resistor-color-duo.spec.js:5:12)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 4 skipped, 5 total
Snapshots:   0 total
Time:        1.08 s
Ran all test suites matching /.\/README.md|.\/babel.config.js|.\/node_modules|.\/package-lock.json|.\/package.json|.\/resistor-color-duo.js|.\/resistor-color-duo.spec.js|.\/yarn.lock/i.

Thank you.

[bobbychicano]

Quick update guys:

I’ve moved on from the exercises I was having trouble with. I added --forceExit in the package.json file so that I could get through them.

I’m currently on the ‘triangle’ exercise and running npm test works smoothly and does not hang.

Thanks y’all for having taken the time to look into this.

[NobbZ]

@NobbZ you have any ideas? Seen this issue on gitter?

Sorry beeing late, just realised this in my inbox by accident…

No, so far this behaviour has not been mentioned in the gitter, and I even asked an ex coworker (the only one I know im my proximity who has done JS for quite a while now) if he had observed something like this before, though he hasn’t as well.