make the syntax error message more helpful for TS users #11807
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I got this error when trying to use jest with typescript. Turns out the info I needed was on https://jestjs.io/docs/getting-started#using-typescript : I needed to install babel and create babel.config.js
Codecov Report
@@ Coverage Diff @@
## main #11807 +/- ##
=======================================
Coverage 69.04% 69.04%
=======================================
Files 312 312
Lines 16366 16366
Branches 4746 4746
=======================================
Hits 11300 11300
Misses 5039 5039
Partials 27 27
Continue to review full report at Codecov.
|
SimenB
requested changes
Sep 17, 2021
| @@ -45,6 +45,7 @@ Here's what you can do: | |||
| ${DOT}If you are trying to use ECMAScript Modules, see ${chalk.underline( | |||
| 'https://jestjs.io/docs/ecmascript-modules', | |||
| )} for how to enable it. | |||
| ${DOT}If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript | |||
There was a problem hiding this comment.
should use chalk.underline as above
SimenB
changed the title
AndrewSouthpaw
added a commit
to AndrewSouthpaw/jest
that referenced
this pull request
Sep 23, 2021
…nsform-ignore-patterns * 'main' of https://github.com/facebook/jest: (38 commits) chore: update `npm` instructions in README (jestjs#11890) chore: force patched version of ansi-regex (jestjs#11889) chore: update lockfile after publish v27.2.1 chore: update changelog for release make the syntax error message more helpful for TS users (jestjs#11807) fix: include path to test file in "after teardown" error (jestjs#11885) docs: add link to the typescript integration instructions (jestjs#11806) fix: properly return mocks when using jest.isolatedModules (jestjs#11882) chore: remove node version pinning from CI (jestjs#11866) chore: remove node 13 as condition in some tests (jestjs#11880) chore: fix typo in docs chore: update lockfile after publish v27.2.0 chore: roll new website version chore: update changelog for release chore: update lock feat: support `conditions` from test environments (jestjs#11863) Revert "chore: remove unneeded yarn patch for react native (jestjs#11853)" chore: supress experimental warnings in tests ...
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I got this error when trying to use jest with typescript. Turns out the info I needed was on https://jestjs.io/docs/getting-started#using-typescript : I needed to install babel and create babel.config.js
Test plan
none