Seems good to me. Native JS over gulp was a decision made by @dgt41 . He's the person to explain the rational :)

@asika32764 sorry for delayed answer, so here is a hint towards where we are aiming with this: Dev tools

@dgt41 It will be great if we have our own packager to help developers like Laravel Mix did.

However, I have ever worked with Gulp, Webpack and Laravel Mix, and I have some suggestion that if we create our own packager and based on some core library (if not based on vanilla JS), we should choose Gulp rather than webpack.

There are some reasons:

1. Gulp is a script manager which help use handle multiple standalone files, while the main purpose of webpack is that bundle all files to one file, it is not suitable for Joomla (Since we use php handle dependencies).
2. Webpack must uses plugins to extract standalone files from main entry file, it is an ugly process and make the config file not human readable. And Gulp did will on this part because of pipe line syntax.
3. Gulp is more flexiable, there is a case that I want to create sourcemap only for non-minified file, Gulp pipe line is able to do this but webpack contains sourcemap mark on both minified and non-minified files and it is hard to remove it in the process (Webpack logic is buiild all first -> then separate them, see).
4. Webpack unable to handle symlinks but Gulp does.

I'm not mean webpack is bad. The main benefit of using webpack is based on it's loaders since webpack's task is to auto load all dependencies and bundle them. It is good for pure frontend projects. And Gulp more like a Makefile to help use compile our codes automatically.

Just personal opinion and share some experience after using Mix.

I'm also creating a Gulp wrap for my framework similar to Laravel Mix, see: https://github.com/ventoviro/windwalker-fusion/blob/master/test/gulpfile.js