Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why-is-node-running package fails on: Cannot find module 'internal/linkedlist' from 'core.js' #3569

Closed
capaj opened this issue May 14, 2017 · 6 comments

Comments

@capaj
Copy link
Contributor

capaj commented May 14, 2017

Do you want to request a feature or report a bug?
bug
What is the current behavior?

node --expose-internals node_modules/.bin/jest admin
 FAIL  test/api/admin.spec.js
  ● Test suite failed to run

    Cannot find module 'internal/linkedlist' from 'core.js'
      
      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:172:17)
      at timers.js:4:11
      at NativeModule.Object.<anonymous>.NativeModule.compile (node_modules/why-is-node-running/core.js:108:3)
      at Function.Object.<anonymous>.NativeModule.require (node_modules/why-is-node-running/core.js:52:16)
      at Object.globalTimeouts (node_modules/why-is-node-running/core.js:14:31)

What is the expected behavior?
it resolves the internal/linkedlist module

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
jest 20.0.0,
ubuntu 17.04
node 7.10.0

@rogeliog
Copy link
Contributor

rogeliog commented Jun 8, 2017

I'm having some trouble reproducing it, do you mean providing a small repro case?

Does node_modules/.bin/jest admin also give that error?

@CMTegner
Copy link

CMTegner commented Jun 9, 2017

@rogeliog Here's a repo that you can clone to reproduce the issue: https://github.com/CMTegner/jest-3569

Reproducible on macOS Sierra (10.12.5), node 8.1.0, npm 5.0.3.

@thymikee
Copy link
Collaborator

thymikee commented Oct 5, 2017

This is an issue with why-is-node-running package: mafintosh/why-is-node-running#7
Not much we can do probably.

@thymikee thymikee closed this as completed Oct 5, 2017
@PatrLind
Copy link

This seems to be solved by running node with --expose-internals (node --expose-internals node_modules/jest/bin/jest.js --testMatch **/testing/*.spec.ts), but I cannot get it to work with jest.

Is jest opening other node processes internally?

@SimenB
Copy link
Member

SimenB commented Jan 24, 2018

Yes. Try to run with -i/--runInBand, maybe that helps?

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants