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.
Opps, Something went wrong. Check the terminal for exact error message!
See original GitHub issueIs 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:
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`);
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:11 (2 by maintainers)
Top Results From Across the Web
I keep getting "oops! something went wrong" when i try to run it ...
Hi! The message in the app is usually shown when Prodigy itself raises an error and stops the server. If you go back...
Read more >7 reasons for Laravel "something went wrong" error, and how ...
Laravel shows a cryptc "something went wrong" error when the app fails. Here are the top 7 reasons for this error, and how...
Read more >I get the error "Oops, something went wrong" when trying to ...
On your device, go to a browser where you're signed in, like Chrome. Go to myaccount.google.com. In the top right, select your profile...
Read more >Git happens! 6 Common Git mistakes and how to fix them
Oops … I spelled that last commit message wrong ... to where it was before you made changes, before finally checking out your...
Read more >something went wrong try reloading the page
my spotify is fine on all my other devices logged into this account ... Press CMD+Search and search for Terminal.app; Enter the following...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
same issue +1
@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” ] },