Introduce gulp

[thumbnail]

Fixes #3, also closes #4

• add css task
  • converts scss, autoprefixes, concatinates and minifies into 1 css file
• add js task
  • polyfils, babelifies, concatinates and uglifies into 1 js file
  • particleJS doesn't like the 'use strict'-preset; fix this
  • svg.easing.js has broken syntax, babel can't deal with it (missing var somewhere)
• add serve task
  • run assets tasks on watch
  • start livereload
  • start webserver
• move all dependencies to package.json
• add build task that just puts all the files in in one folder

Results

the site is at best about 150ms faster. it doesn't matter a lot though. It was mostly practise and wider support for es6 that #3 addressed.

[thumbnail]

convert to pump

[hampterhub]

wouldn't it be nicer to use one export

exports.build = series(
  clean,
  parallel(
    cssTranspile,
    series(jsTranspile, jsBundle)
  ),
  parallel(cssMinify, jsMinify),
  publish
);

[thumbnail]

As described in the description of the PR there's still a build-task to be made, which combines both.

I'd like the css and js tasks to be available independent of eachother anyway.

[hampterhub]

Even if you export everything at ones they should be available as their own tasks using gulp [task name]

[hampterhub]

let jekyll = spawn('jekyll', ['serve', '--livereload'], { stdio: 'inherit' });

wouldn't it be to use gulp-watch, then you can also set the server parameters.

[thumbnail]

you can pass configuration using the _config.yml file in the root. less convenient than a argument but i don't feel like supporting arguments directly to be honest.

[xvilo]

what about:

"scripts": {
  "gulp": "node ./node_modules/gulp/bin/gulp.js <task-name>" 
}

Then: $ npm run gulp

[xvilo]

just do npm install. Thats all you need.

[thumbnail]

As you can see in the builds, such as build 67 it didn't appear to work. I tried debugging using ssh on the machine and only with all three npm installs it appeared to install gulp-cli

[xvilo]

So what you do, is create the npm command I commented, then just require gulp 3.x and then change line 21 to npm run gulp

[hampterhub]

@xvilo i refactored your solution into #18 thanks for the advice.

i also learned that when using npm run there is no need to use a full path like node ./node_modules/gulp/bin/gulp.js <task-name> since npm run will add the packages to the path when you use it.

[xvilo]

Not needed

[thumbnail]

It didn't seem to work without, but since i explicitly install it in the circleci config I might be able to delete it. also more people suggest gulp-cli is needed

[thumbnail]

regarding the scripts-config; intresting construction, not sure what it brings me though? could you elaborate?

[xvilo]

Then you don't have to install a lot of unrelated packages, or install things globally in the CI (use containers with the specific tools already pre installed). You can ofcourse run the commands from your ci config file. But why not add it as a nice npm run 'command'. It was just another solution to the problem. There are meerdere wegen to Rome

[hampterhub]

looks good