This repository has been archived by the owner on May 29, 2019. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yay! I hope this will be made into 2.0.0-beta.5 soon.
thanks!
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SpaceK33z do you know when this will get a release?
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@graingert don't know, I don't have npm publish permissions
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When will beta-5 be released then
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sokra can we get a release on this. Maybe an rc too?
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
super cool! waiting for the release, till then my shrinkwrap is broken :(
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just found this most fantastic workaround until a release is pushed:
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sokra @TheLarkInn – any chance we can publish a new version, e.g. beta5? Having to point to this SHA instead of using a proper npm version is causing us serious grief at @getsentry, where we're trying to use Webpack 2 rc3 live.
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's really not a healthy situation when a PR merger doesn't have rights to publish a fix and the project owner just ignores the project.
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SpaceK33z can you publish to another npm package?
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@graingert lol, hold your horses, young man.
when @sokra comes out of his ivory tower he'll publish this thing, no doubts.
probably so busy landing that 2.2.0 release.
I'm sure his email is disabled otherwise he'd get hundreds of github notifications per day.
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@halt-hammerzeit @benvinegar @graingert Hey sorry! Everyone has different availabilities (which means we are all not around just yet) and as a team we have to ensure there isn't any other critical low hanging fruit before we publish. I'm actively on this ensuring we will get you these changes.
I really appreciate your patience and kindness in the matter.
cbd4690There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@halt-hammerzeit @benvinegar @TheLarkInn ah it looks like v2.0.0-beta.5 is out