gulp 4 is out!

[phated]

Hey @frankwallis - I wanted to let you know that gulp 4 is out. I'd love to get the Custom Registry stuff finished here and get it published. We recommend gulp-hub as a Custom Registry for dynamically loading tasks now.

[frankwallis]

This is published for version 4 as gulp-hub@next I'm not sure what else there is to do TBH but I've not really been following recent changes to gulp4

[ginnsquad]

@phated I ran into issues using gulp-hub with gulp 4 and wrote my solution in an old issue here: https://github.com/gulpjs/undertaker/issues/83#issuecomment-405325906

[chmerk]

Hey guys,

I'm curios: On the official gulp website it's not recommended to use gulp.task anymore (https://gulpjs.com/docs/en/api/task). But as far as I can tell, gulp-hub doesn't work with the "new" way of exporting tasks.

Will gulp-hub support this style of defining tasks in the near future? Or how does it go together that gulp-hub is the recommended way to split up your tasks? (Kind of the same problem as in @ginnsquad 's issue!)

Thanks, Chris

[frankwallis]

gulp-hub for gulp4 was previously only published as gulp-hub@next so I suspect you were using the version for gulp3. I have now published the gulp4 version as @latest so that is what you should now get if you run npm install gulp-hub

[chmerk]

@frankwallis thanks for the quick reply! :-) No, I installed gulp-hub@next (4.2.0).

So, should [email protected] detect tasks which are not registered via gulp.task("myTask", myTask) but exported (e.g. via module.exports = myTask)?

If so, how exactly do they have to be defined?

[frankwallis]

TBH I'm not sure what the current status is as it is a couple of years since I last looked at this..

[S1SYPHOS]

Would be a blast to see your plugin going, mate! :rice_ball: