Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Generate a jest.config.js to integrate with tools like VS Code's Jest plugin #118

Closed
arvigeus opened this issue May 29, 2019 · 2 comments
Closed

Generate a jest.config.js to integrate with tools like VS Code's Jest plugin #118

arvigeus opened this issue May 29, 2019 · 2 comments
Labels
scope: integration Related to an integration, not necessarily to core (but could influence core) solution: duplicate This issue or pull request already exists

Comments

@arvigeus
Copy link

Current Behavior

Some tools like VSCode's Jest plugin fail. Running tests normally works fine

Expected behavior

Tests should work

Suggested solution(s)

Add "present": "ts-jest" to createJestConfig.
@jaredpalmer
Copy link
Owner

I think someone tried to solve this in #75, but this generated absolute paths to tsdx's jest plugins.

@jaredpalmer jaredpalmer changed the title Add "present": "ts-jest" to jest config Add "preset": "ts-jest" to jest config May 30, 2019
@agilgur5
Copy link
Collaborator

agilgur5 commented Mar 9, 2020

Duplicate of #270

I'm not sure why this mentions the ts-jest preset since tsdx test doesn't use it (maybe it did at some point?)

@agilgur5 agilgur5 closed this as completed Mar 9, 2020
@agilgur5 agilgur5 added solution: duplicate This issue or pull request already exists scope: integration Related to an integration, not necessarily to core (but could influence core) labels Mar 9, 2020
@agilgur5 agilgur5 changed the title Add "preset": "ts-jest" to jest config Generate a jest.config.js to integrate with tools like VS Code's Jest plugin Mar 9, 2020
@agilgur5 agilgur5 mentioned this issue Mar 18, 2020
Open
Repository owner locked as resolved and limited conversation to collaborators Nov 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
scope: integration Related to an integration, not necessarily to core (but could influence core) solution: duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jaredpalmer @arvigeus @agilgur5