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

Is it possible to have a separate webpack config for tests? #223

Closed
axelson opened this issue Mar 22, 2016 · 4 comments
Closed

Is it possible to have a separate webpack config for tests? #223

axelson opened this issue Mar 22, 2016 · 4 comments

Comments

@axelson
Copy link

axelson commented Mar 22, 2016

We have a separate alias that is only used for tests and it would be nice to have this supported in eslint-plugin-import.

@benmosher
Copy link
Member

You can re-specify import/resolver in an .eslintrc for your test folder.

I do this for one of my projects, where I use the webpack resolver for ./src and the stock node resolver for ./test.

I think this covers what you're asking?

@axelson
Copy link
Author

axelson commented Mar 23, 2016

It seems like it should but I'm still having some issues. Might be related
to how the base weback configuration interacts with the test config.
Definitely possible that it's user error.

On Tue, Mar 22, 2016, 11:02 AM Ben Mosher notifications@github.com wrote:

You can re-specify import/resolver in an .eslintrc for your test folder.

I do this for one of my projects, where I use the webpack resolver for
./src and the stock node resolver for ./test.

I think this covers what you're asking?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#223 (comment)

@benmosher
Copy link
Member

Can you provide more details about the folder structure and the contents of the config files?

@benmosher
Copy link
Member

closing for now, let me know if you want to discuss further

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

No branches or pull requests

2 participants