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

module validator #9

Closed
PatrickJS opened this issue Feb 25, 2016 · 7 comments
Closed

module validator #9

PatrickJS opened this issue Feb 25, 2016 · 7 comments
Assignees

Comments

@PatrickJS
Copy link

loaders vs loader and when to use them

@kentcdodds
Copy link
Owner

👍

@jonathanglasmeyer
Copy link
Collaborator

@gdi2290 Are you referring to loader vs. module.loaders?
It's not really clear to me how this "gotcha" could be expressed as an validation rule, apart from the existing spellchecking/whitelisting behaviour. Any thoughts?

@kentcdodds
Copy link
Owner

apart from the existing spellchecking/whitelisting behaviour.

I think the spellchecking behavior will probably cover what @gdi2290 was talking about. I think we can probably close this. Please re-open if you disagree @gdi2290!

@PatrickJS
Copy link
Author

in webpack you can use both loader and loaders so devs would sometimes use an array for loader. Webpack 2 allows for TypeScript just as gulp does so this won't be a problem soon

@kentcdodds
Copy link
Owner

Ah yeah, so we need an actual validator for those before this can be closed.

@kentcdodds kentcdodds reopened this Mar 18, 2016
@jonathanglasmeyer
Copy link
Collaborator

I'm on this.

@jonathanglasmeyer jonathanglasmeyer self-assigned this Mar 20, 2016
@jonathanglasmeyer jonathanglasmeyer changed the title #2 webpack gotcha: loaders vs loader module validator Mar 20, 2016
@jonathanglasmeyer
Copy link
Collaborator

Tackled this in #47.

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

No branches or pull requests

3 participants