-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
6.0.0 #240
6.0.0 #240
Conversation
var firstBuild = true; | ||
|
||
// This empty stream might seem like a hack, but we need to specify all of our files through | ||
// the `entry` option of webpack. Otherwise, it ignores whatever file(s) are placed in here. |
There 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.
Why don't you just start with the webpackStream
then?
There 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.
'cuz I'm a noob. I'll try that
I just realized that simply using |
Hmm... The way gulp should probably be implementing that is to limit the register to only the gulpfile. |
Yeah? I wonder if it's a bug, then. It's working over here. |
We were accidentally binding the context of the function. Luckily, this was never released! Resolves #249
runSequence was added as a stop-gap to prevent Browserify from breaking. New error handling makes it safe to attempt to build even the worst of code. Therefore, runSequence is no longer necessary. Resolves #254
Webpack is now used to build the distributed build.
Resolves #246
Resolves #199
Resolves #264
Removes the need to update two objects. It's too easy to update one and for get the other. It wasn't consistent as it was. And it's in the test/setup directory which seems pretty self explanatory.
This fixes an issue where source maps would not work with Webpack. For more, reference shama/webpack-stream#86
Alright, finally gonna cut this release then start work on the next version, which will use Babel v6! |
Will resolve #236
Todo: