-
Notifications
You must be signed in to change notification settings - Fork 512
Support webpack 2.2 #309
Comments
Guys. Is it really hard to update package.json ? |
Really need this update :'( Christmas is like hell for developers who are still working... |
Try |
Can we avoid non-constructive comments? They're unlikely to motivate maintainers, on the contrary. If I was receiving such comments on one of my repositories, I'd make sure not to fix the issue for a month or two :-) Thanks! |
(Obviously this wasn't for laggingreflex. I wrote my comment before theirs appeared.) |
@MikeLP Sorry for the delay on this. There are some overall large changes we want to make here before we do another publish. There is a lot of tenderloving care that needs to be given to this repo. We have already extended the call for extra support for issues and PR's to our @webpack/contributor-team so once we get some more information, we'll have some folks getting back to you guys. Understand the frustration, and we apologize for dropping the ball. Thank you everyone for the support, and if it is possible you can avoid the PeerDep and install fails by using npm v3 for now! Let me know if anything else needs to be clarified. |
I use shrinkwrap feature of npm. It requires me to satisfy all peer dependencies. |
@TheLarkInn, thanks for the update, but can you please update the peer dependency to not require the beta though? Some people cannot deploy with yarn/npm warnings because of how ops has configured their ci deploy system with fail on warnings. We cannot move beyond |
Looks like a fix to that has been committed: cbd4690. Here's to hoping it'll be released soon... |
I installed latest code via git+https: |
the code in npm haven't been updated :( |
Fix was published in |
Seems that plugin should be published with updated peer dependencies
The text was updated successfully, but these errors were encountered: