The Wayback Machine - https://web.archive.org/web/20200527134544/https://github.com/Raathigesh/majestic/issues/142
Skip to content

/ majestic

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

Jump to bottom

Opps, Something went wrong. Check the terminal for exact error message! #142

Open
alexgorbatchev opened this issue May 7, 2019 · 8 comments
Open

Opps, Something went wrong. Check the terminal for exact error message! #142

alexgorbatchev opened this issue May 7, 2019 · 8 comments
Labels
🦄 Need more info

Comments

@alexgorbatchev
Copy link

@alexgorbatchev alexgorbatchev commented May 7, 2019 •
edited

Is this a bug report or a feature request?

Bug

Version Info

  • Version of Majestic: 1.4.1
  • Version of Jest: 24.7.1
  • Version of Node: 10.13.0
  • Operating System: OSX

Reproduction Repo

Run npx majestic in a folder where yarn jest works fine and has jest.config.js, then I just see this:

image

There's no error message in the terminal and one error in dev console. My jest.config.js looks like this and the project is a yarn monorepo.

module.exports = require('common-module/jest')(`${__dirname}/packages`);
@alexgorbatchev alexgorbatchev changed the title UI doesn't load Opps, Something went wrong. Check the terminal for exact error message! May 7, 2019
@Raathigesh
Copy link
Owner

@Raathigesh Raathigesh commented May 8, 2019

Would you please run majestic with the --debug flag and share a screenshot or the output?
@alexgorbatchev
Copy link
Author

@alexgorbatchev alexgorbatchev commented May 8, 2019

Here's the output from --debug

❯ npx majestic --debug
npx: installed 31 in 5.923s
⚡  Majestic v1.4.1 is running at http://localhost:4000
ℹ Majestic configuration from Package.json:  {}                                      Config Resolver 11:08:03
ℹ Path of resolved Jest script:  .../node_modules/jest
ℹ Resolved Majestic config : {                                                       Config Resolver 11:08:03
  jestScriptPath: '".../node_modules/jest/bin/jest.js"',
  args: [],
  env: {}
}
ℹ Error occured while obtaining Jest cofiguration for coverage report                        Results 11:08:04
@alexgorbatchev
Copy link
Author

@alexgorbatchev alexgorbatchev commented May 8, 2019

If I try to disable coverage, there's no visible change in the output.
@Raathigesh
Copy link
Owner

@Raathigesh Raathigesh commented May 13, 2019

That's unfortunate. Would you be able to provide a sample repository?
@xavierbriole
Copy link

@xavierbriole xavierbriole commented May 15, 2019

Same error
@jukbot
Copy link

@jukbot jukbot commented Aug 24, 2019

same issue +1
@GowthamX
Copy link

@GowthamX GowthamX commented Mar 9, 2020

@Raathigesh - Could you please let me what are the details needed please?
I am facing the same issue too, so i can share the same
@GowthamX
Copy link

@GowthamX GowthamX commented Mar 9, 2020

@Raathigesh - works now. Please ignore.
Added the below in package.json which is given in Issue-87. 👍

"majestic": {
"jestScriptPath": ".\node_modules\jest\bin\jest.js",
"args": [
"test"
]
},
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🦄 Need more info
5 participants
@alexgorbatchev @Raathigesh @jukbot @xavierbriole @GowthamX
You can’t perform that action at this time.