question-mark
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: It doesn't recognise the project

See original GitHub issue

Is this a bug report or a feature request?

🐛.

Version Info

  • Version of Majestic: 0.1.0
  • Version of Jest: latest
  • Version of Node: 8.7
  • Operating System: OS X

This is my configuration on package.json

  "jest": {
    "moduleDirectories": [
      "./ui-lib/src",
      "./ui-lib/node_modules",
      "node_modules",
      "./obs",
      "./obs/node_modules"
    ],
    "moduleNameMapper": {
      "^.+\\.(jpg|jpeg|png|gif|eot|webp|svg|ttf|woff|woff2)$": "<rootDir>/jest/fileMock.js",
      "^.+\\.(css|scss)$": "identity-obj-proxy",
      "frontend/ui-lib(.*)$": "<rootDir>/ui-lib/$1"
    },
    "transform": {
      "^.+\\.js?$": "babel-jest",
      ".*": "<rootDir>/node_modules/jest-css-modules"
    },
    "transformIgnorePatterns": [
      "/node_modules/(?!(frontend)/).*/",
      "obs/node_modules/(?!(frontend)/).*/"
    ],
    "setupFiles": [
      "raf/polyfill",
      "<rootDir>/jest.init.js"
    ],
    "collectCoverage": true,
    "coverageDirectory": "./coverage",
    "coverageReporters": [
      "html",
      "text-summary"
    ]
  },

No files are shown up in the sidebar, when I press the run test, nothing happens. No error displayed either though.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
Raathigeshcommented, Jan 3, 2018

The issue is you are relying on the default test regex pattern and your configuration does not have a test regex pattern or a test match pattern. I completely overlooked the defaults of these patterns so that’s why it doesn’s show up.

I’ll have a release ready with this fix in a couple of days. But if you need to try the app, just add the following to the jest config.

"jest": {
    "testMatch": [ '**/__tests__/**/*.js?(x)', '**/?(*.)(spec|test).js?(x)' ]
// other configs
}

let me know if you managed to get it to work after this workaround.

0reactions
Raathigeshcommented, Jan 11, 2018
Read more comments on GitHub >

github_iconTop Results From Across the Web

[BUG] projectile does not recognize .projectile files as ... - GitHub
In a multi-project git repository, using SPC SPC ( projectile-find-file ) is not respecting .projectile file anymore, and filters through ...
Read more >
Troubleshoot broken references - Visual Studio - Microsoft Learn
The project's reference path is incorrect or incomplete. ... the reference can't be found and an error appears in the Task List.
Read more >
Added a new Issue Type "Bug" which is not appearin...
Hi, We created an issue type Bug and created few bug tickets and assigned them to the developers. These tickets are displayed in...
Read more >
c# - Namespace not recognized (even though it is there)
This is a problem in Visual Studio (I would even go so far as to call it a bug). AutoMapper requires assemblies that...
Read more >
Help! The BugHerd sidebar isn't appearing!
BugHerd sidebar not appearing when you first leave feedback? If you're setting up your first project, you need to give feedback or report......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found