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

Support webpack 2.2-rc #695

Merged
merged 1 commit into from Jan 19, 2017
Merged

Support webpack 2.2-rc #695

merged 1 commit into from Jan 19, 2017

Conversation

graingert
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Dec 21, 2016

Coverage Status

Coverage remained the same at 94.86% when pulling b69f719 on graingert:patch-1 into e26e898 on benmosher:master.

@graingert
Copy link
Contributor Author

@benmosher I can't work out why appveyor is failing

@jfmengels
Copy link
Collaborator

The appveyor error is not related. The same error happens on other PRs too. I think that it's an error on their side.

I'm fine with this change, but would it not be possible to instead say that we support webpack 2.x.x (rc or not)? Since it's a release candidate, it's very unlikely to have breaking changes that will affect this plugin. Just to avoid having to re-do a similar PR when the final v2 release is made.

@graingert
Copy link
Contributor Author

This seems to be what the official (under the webpack project on github) loaders and plugins do

@graingert
Copy link
Contributor Author

@jfmengels @benmosher any update on merging this?

@ChaseBro
Copy link

Is there anything additional required here? I would love to see this get merged as it's blocking the upgrade to Webpack 2. Happy to help if there's anything else needed.

@graingert
Copy link
Contributor Author

@benmosher this seems to be blocking a fair few projects...

@ChaseBro
Copy link

ChaseBro commented Jan 9, 2017

Will this be merged? It's been almost 3 weeks since it was originally submitted (admittedly including the holidays), but I would really love to keep using this plugin if at all possible.

@graingert
Copy link
Contributor Author

@benmosher now that extract-text-webpack-plugin is out. This is the last project blocking me from enjoying the glory of webpack 2rc.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.863% when pulling fc9581e on graingert:patch-1 into c975742 on benmosher:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.863% when pulling fc9581e on graingert:patch-1 into c975742 on benmosher:master.

@coveralls
Copy link

coveralls commented Jan 19, 2017

Coverage Status

Coverage remained the same at 94.863% when pulling fc9581e on graingert:patch-1 into c975742 on benmosher:master.

@coveralls
Copy link

coveralls commented Jan 19, 2017

Coverage Status

Coverage remained the same at 94.863% when pulling fc9581e on graingert:patch-1 into c975742 on benmosher:master.

@benmosher benmosher merged commit b6c2468 into import-js:master Jan 19, 2017
@graingert graingert deleted the patch-1 branch January 19, 2017 12:12
benmosher added a commit that referenced this pull request Jan 19, 2017
@benmosher
Copy link
Member

published as v0.8.1 of the webpack resolver 😎

@benmosher
Copy link
Member

btw, thanks for reviewing @jfmengels!

@jfmengels
Copy link
Collaborator

jfmengels commented Jan 19, 2017

btw, thanks for reviewing @jfmengels!

No problem. I'll try to do some more, I've been neglecting too many projects lately...

@graingert Do we need to make a similar change for webpack 2.2.0-alpha and webpack 2.2.0?

@graingert
Copy link
Contributor Author

should just work for 2x

@jfmengels
Copy link
Collaborator

Sorry. Did you mean that we should make a change to support webpack 2-x-x, or that this is already good? The former, right?

@graingert
Copy link
Contributor Author

@jfmengels ^2.1.0 means >=2.1.0 <3.0.0

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

Successfully merging this pull request may close these issues.

None yet

5 participants