Add NSHipster.com to List of Examples

[mattt]

[mattt]

Checks are failing, but it doesn't look like it was caused by this commit in particular.

Here's what I got when running a fresh clone of the repository (node v8.10.0, npm 6.4.1):

$ npm run start
fnm: It seems 'node' is not a valid version number.
Hint: Examples of valid node versions:
       v5.10.1
        latest
          0.12
           lts

> victor-hugo@1.0.0 start /Users/mattt/Sites/jamstack.org
> gulp server

[11:12:51] Failed to load external module @babel/register
[11:12:51] Requiring external module babel-register
...

[mattt]

9990fad fixed the "It seems 'node' is not a valid version number." error, but checks are still failing on 11:26:47 AM: > gulp build-preview.

[mattt]

I just realized that I was previewing locally with gulp server instead of gulp build, so I was confused why it was succeeding locally but failing on deploy. I can now replicate the issue locally.

This appears to be related to gulpjs/gulp#2246. It looks like our options are to either upgrade to gulp@next to support new Node versions or specify an older version of node to a version compatible with 3.9.1.

[netlify]

Deploy preview for jamstack-site ready!

Built with commit c6043f8

https://deploy-preview-138--jamstack-site.netlify.com

[mattt]

Alright, I updated to Gulp 4 with c6043f8. This required some slight modifications to gulpfile.babel.js to migrate to the new task API (instead of an array of dependencies, you specify gulp.series(...) or gulp.parallel(...)).

[philhawksworth]

Closed by #285

[mattt]

Awesome. Thanks so much, @philhawksworth!