Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: Unexpectedly open node.js file

See original GitHub issue

Version

27.0.6

Steps to reproduce

Clone my repo at https://github.com/Mycrl/jest-bug-report
yarn install
yarn test
You will see that jest opened the node.js file, but did not run

Expected behavior

I want to see jest start running

Actual behavior

I think jest opened the node.js file under the directory by mistake when calling the node command

Additional context

No response

Environment

System:
    OS: Windows 10 10.0.19043
    CPU: (6) x64 AMD Ryzen 5 3500X 6-Core Processor
  Binaries:
    Node: 14.17.3 - D:\Node\node.EXE
    Yarn: 1.22.11 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.20.5 - D:\Node\npm.CMD

Issue Analytics

State:
Created 2 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

sigveiocommented, Aug 25, 2021

Hey @Mycrl!

Thanks for providing a repo 👍

Screenshot 2021-08-25 at 11 44 16

I’m not able to reproduce what you describe; seems to run fine here.

0reactions

github-actions[bot]commented, Nov 23, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

Top Results From Across the Web

6 reasons your Node.js apps are failing

Excessive memory usage, which may result in an out-of-memory error; Unresponsive application, possibly looping or hanging; Poor performance; Crash or abort in ...

NodeJs: Unexpected token < error in javascript file

The problem with your code is that, for each request, it reads treeDemoinJavaScript.html , adds a header value of text/html , and writes...

15 Common Error Codes in Node.js and How to Fix Them

15. EPERM · Close all instances of your editor before rerunning the command (maybe some files were locked by the editor). · Clean...

require.resolve() on Node 10 unexpectedly returns local ...

It returns /tmp/bug/qunit.json . Additional information. This works as expected on Node.js v14.5.0, but it is broken on Node v10 LTS. As ...

Let It Crash: Best Practices for Handling Node.js Errors on ...

When a JavaScript error is not properly handled, an uncaughtException is emitted. These suggest the programmer has made an error, and they ...