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

Update peerDependencies to include Webpack 2 #208

Merged
merged 1 commit into from
Feb 3, 2016
Merged

Conversation

gaearon
Copy link
Member

@gaearon gaearon commented Feb 3, 2016

Webpack 2 does not seem to have changes breaking this loader. In this PR, we explicitly enable the latest beta (since we have to specify exact prerelease versions in semver), as well as the stable 2.x when it comes out.

@gaearon
Copy link
Member Author

gaearon commented Feb 3, 2016

Note: I’m specified as the “owner” here but I don’t publish packages so it’s up to the actual maintainers to merge this.

Couto added a commit that referenced this pull request Feb 3, 2016
Update peerDependencies to include Webpack 2
@Couto Couto merged commit 806077e into master Feb 3, 2016
@Couto
Copy link
Member

Couto commented Feb 3, 2016

I'm just trying to fix the travis error, and I'll publish the package right after.
Thanks for the PR :)

@Couto
Copy link
Member

Couto commented Feb 4, 2016

Travis is taking ages to start with the builds.
This is already in npm with the version v6.2.2

@gaearon gaearon deleted the gaearon-patch-1 branch February 4, 2016 03:50
@gaearon
Copy link
Member Author

gaearon commented Feb 4, 2016

Thank you for quick response!

@adamdicarlo
Copy link

webpack 2 is now at 2.0.7-beta. Is it possible to specify "2.x-beta" or some such to avoid npm warning? or is the warning desired?

@Couto
Copy link
Member

Couto commented Feb 7, 2016

The warning is not exactly desired, but as far I can tell, npm doens't work well with ranges and pre-releases.

@gaearon
Copy link
Member Author

gaearon commented Feb 7, 2016

Yeah, you can’t include all future pre-releases.
It might be easier for you to just use npm@3 that does not force peerDeps.

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

Successfully merging this pull request may close these issues.

3 participants