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.

Jest config do not get update when lib or app is deleted by remove schematic

See original GitHub issue

Current Behavior

When lib or app is deleted by remove schematic the root level jest.config.js is not updated by removing the entry of deleted project. I have to manually delete the entry from this file.

yarn nx generate remove <lib-name>

Expected Behavior

jest.config.js need to automatically update by deleting the entry of deleted project

Steps to Reproduce

Step 1: Create new lib with below command

yarn nx g @nrwl/node:library <lib-name>

Step 2: Check root level jest.config.js for entry of newly created lib as result of Step 1

Step 3: Delete lib created in Step 1 by below command

yarn nx generate remove <lib-name>

Step 4: Check root level jest.config.js again the entry of newly created lib as result of Step 1 is still there

Environment

Note: nx is shown as not found below because as i did not installed nx globally

nx : Not Found @nrwl/angular : Not Found @nrwl/cli : 10.3.0 @nrwl/cypress : 10.3.0 @nrwl/eslint-plugin-nx : 10.3.0 @nrwl/express : Not Found @nrwl/jest : 10.3.0 @nrwl/linter : 10.3.0 @nrwl/nest : Not Found @nrwl/next : 10.3.0 @nrwl/node : 10.3.0 @nrwl/react : 10.3.0 @nrwl/schematics : Not Found @nrwl/tao : 10.3.0 @nrwl/web : 10.3.0 @nrwl/workspace : 10.3.0 typescript : 4.0.3

Issue Analytics

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

github_iconTop GitHub Comments

1reaction
mehrad-rafighcommented, Dec 8, 2020

@etkachev My pleasure! I opened another issue for the move schematic and am currently adjusting the schematic. I already wrote the test for it, so I guess I will create a PR during the evening

1reaction
mehrad-rafighcommented, Dec 8, 2020

@etkachev I already guessed it. I will try to open a seperate PR for the move schematics. Alright?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting - Jest
Troubleshooting. Uh oh, something went wrong? Use this guide to resolve issues with Jest. Tests are Failing and You Don't Know Why​.
Read more >
Jest + Typescript + Absolute paths (baseUrl) gives error
I was struggling with the same problem and actually it turns out that a simple change seems to do the trick.
Read more >
Integrate Jest into an Angular application and library
If you don't got the Angular CLI installed, you can install it ... We also have to delete the karma.config.js and test.ts files...
Read more >
How to Test Your Apps using Jest, Testing Library, Cypress ...
This will help clarify the many ways in which a software can be tested and better understand the tools we're going to present...
Read more >
Migration Guide | Cypress Documentation
This Node.js version will no longer be supported when installing ... that relied on the application to persist between tests may have to...
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