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

Fix #666: resolve config from source file #993

Closed
wants to merge 2 commits into from

Conversation

Billy-
Copy link

@Billy- Billy- commented Jan 5, 2018

when a relative configPath is passed, it should be resolved relative to the source file, not the imported file.
Fixes #666

when a relative `configPath` is passed, it should be resolved relative to the source file, not the imported file.
Copy link
Member

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

Can you please add a regression test that would have caught this?

@ljharb ljharb added the resolver label Jan 5, 2018
@Billy-
Copy link
Author

Billy- commented Jan 5, 2018

Sure, I'll take a look.

@Billy-
Copy link
Author

Billy- commented Jan 5, 2018

Sorry, I think I jumped the gun a bit there. It coincidentally worked (until I ran tests).

@Billy- Billy- closed this Jan 5, 2018
@Billy-
Copy link
Author

Billy- commented Jan 5, 2018

Perhaps worth mentioning that the variable naming (source and file) is very confusing! source is the file being imported, and file is the source file being linted...

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

Successfully merging this pull request may close these issues.

Webpack resolver looks for custom webpack config in packages with jsnext:main
2 participants