From 76428647b58ed6c9ad154d5965e24ecddef25be1 Mon Sep 17 00:00:00 2001 From: Biki-das Date: Thu, 16 Feb 2023 10:09:54 +0530 Subject: [PATCH] Fixed wrong debug command --- content/docs/how-to-contribute.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/how-to-contribute.md b/content/docs/how-to-contribute.md index 2286084c12c..86fdb0c870d 100644 --- a/content/docs/how-to-contribute.md +++ b/content/docs/how-to-contribute.md @@ -89,7 +89,7 @@ The core team is monitoring for pull requests. We will review your pull request 3. If you've fixed a bug or added code that should be tested, add tests! 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development. 5. Run `yarn test --prod` to test in the production environment. -6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect". +6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect". 7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`). 8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files. 9. Run the [Flow](https://flowtype.org/) typechecks (`yarn flow`).