-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[feature] make context.getCwd()
available in resolver
#2108
Comments
When available, that seems like something we could provide, altho I'm not clear on when the value would be different than |
It's about IDE/editor integration actually, it can be opened in parent/child folder, did you read through my linked issue? 🤣 |
I looked, but it’s long. an IDE should also always be opened from the root of the repo. Either way, it’d be fine to provide the proper value when available. |
I feel like these issues could easily be solved by adding a |
I proposed to adding new arguments into current resolver API without any breaking change at #2447 (comment) @ljharb How do you think? declare function resolve(
source: string,
file: string,
config: object,
options?: {
parser: string;
parserOption: object;
context: object;
}
): { found: Boolean; path: String? }; |
As long as that actually has no breaking change, that sounds great. |
OK, I'll raise a PR for it. |
context: import-js/eslint-import-resolver-typescript#74 (comment)
process.cwd()
could be incorrect,context.getCwd()
is the replacement.The text was updated successfully, but these errors were encountered: