-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Fix/find project root provides wrong root package json path #162
Fix/find project root provides wrong root package json path #162
Conversation
Hey, actually I am sure everyone is thankful for some tests, so cheers for adding this one and fixing a bug there. I haven't checked the pr yet, but from a first look, just wondering if babel is needed here. Can't we just use |
TBH my Typescript/Jest knowledge is fresh, so probably. I'll look into that and see if we can trim some of that fat! |
Poking around more - the Babel use comes right from the Jest Docs: https://jestjs.io/docs/getting-started#using-typescript Seems there are some floating SO posts regarding how to bypass it, but it may be sketchier or less stable that just adding the extra babel dependencies for now. Just my opinion though! |
Hey @tonyt-adept , about tests, what you need is to add |
Thanks for laying it out guys! Appreciate the assist! Hope she's lookin good now. I did |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @tonyt-adept , looks perfect to me. let me merge it.
And welcome to contribute more.
🎉 This PR is included in version 1.16.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
PR add's some fluff for the singular Jest test... More than happy to rip that out before final Merge, just wanted to showcase the error before/after.
Also regarding the fix - I tried to leave the original
findUp
logic intact by queuing off ofstring vs. string[]
however I understand if you guys would like to go down another path to keep things a bit more clear & concise in there! Just let me know the guidelines and I'm happy to refactor.Thanks again!