Nested projects are ignored
See original GitHub issueDo you want to request a feature or report a bug? Bug
What is the current behavior?
Running jest
in monorepo ignores projects in packages.
Minimal repo: https://github.com/deftomat/jest-nested-projects-issue
What is the expected behavior? Should run all projects in all packages. In another words: Should run nested projects.
Environment Jest: v22.1.4 Node: v8.9.4 OS: macOS High Sierra
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Git Ignore common directories in subprojects - Stack Overflow
But none seems to be working for me. git status for the container project still lists changes from these target folders in the...
Read more >Sub-projects are ignored? - Gradle Forums
Problem is that they aren't. The sub-projects are not being built when running the build.gradle in the parent project. It appears that Gradle ......
Read more >File nesting rules for Solution Explorer - Visual Studio (Windows)
You can tell Visual Studio to ignore solution-specific and project-specific settings, even if the files exist on disk, by enabling the option ...
Read more >448117 – "Hide folders of physically nested modules ... - Bugs
Bugzilla – Bug 448117 "Hide folders of physically nested modules" preference ignored when creating a new Module Last modified: 2021-04-19 13:24:28 EDT.
Read more >Ignoring Files And Directories - TortoiseSVN
In most projects you will have files and folders that should not be subject to version control. These might include files created by...
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 FreeTop 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
Top GitHub Comments
I think I’d be happy for this to be supported. We just need to change the project merging to be recursive.
@rolandjitsu
Well, kind of. We, for example, using TypeScript in a few packages and to make it works, these packages have a necessary config. Global Jest’s config doesn’t know anything about TS.
So, it looks like Jest is using a package’s config, however, it ignores some parts. Like in this issue, it ignores
projects
properties and also, as mentioned here, it ignores global setup/teardown.Jest is awesome and probably the best test framework but projects feature is highly unpredictable. At least, for me 😉