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.

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

Change the package entry point to preprocessor.js itself #363

Merged

Conversation

martijnthe
Copy link
Contributor

This way, the "ts-jest" package name can be used as Jest transform, instead of specifying the path to preprocessor.js.
The latter did not work when the ts-jest package had been hoisted to a parent folder (for example by lerna).

Fixes #361

This way, the `"ts-jest"` package name can be used as Jest transform, instead of specifying the path to preprocessor.js.
The latter did not work when the ts-jest package had been hoisted to a parent folder (for example by lerna).

Fixes kulshekhar#361
@kulshekhar
Copy link
Owner

@martijnthe Thanks for the PR!

I'll review this as soon as I can. In the meanwhile, I have one question - after this is merged, will the current way of specifying the transformer continue to work? It should, to avoid breaking stuff

@martijnthe
Copy link
Contributor Author

In the meanwhile, I have one question - after this is merged, will the current way of specifying the transformer continue to work? It should, to avoid breaking stuff

@kulshekhar It should yes, I left the existing preprocessor.js intact, exactly for that reason.

@GeeWee
Copy link
Collaborator

GeeWee commented Nov 6, 2017

I didn't review the code - but loving the idea.

kulshekhar
kulshekhar previously approved these changes Nov 7, 2017
Copy link
Owner

@kulshekhar kulshekhar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. I'll leave this up for about a day to see if anyone else has any comments

@martijnthe
Copy link
Contributor Author

@kulshekhar thanks, sgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants