fix: Use only 4.1.x version of superstatic not 4.x

[vertein]

Superstatic version 4.2 introduced a dependency on shrink-ray, which introduced a dependency on node-zopfli, which introduces the need for a c compiler when building. We're using the mvn deploy command to push out new releases. This calls a mvn exec command 'npm install'. npm install still 'succeeded' before, but exited with a code 1 (definitions of succeed vary), causing the mvn deploy command to fail.

---

Contributor License Agreement adherence:

• This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

[ChristianMurphy]

LGTM,

@vertein what version of npm are you running?
Some of the integrity hashes in package-lock.json are dropping from sha512 to sha1 which seems somewhat unexpected.

[ChristianMurphy]

🍎 OS X build is failing with

/Users/travis/build/UW-Madison-DoIT/uw-frame/node_modules/less/lib/less/functions/function-caller.js:1
(function (exports, require, module, __filename, __dirname) { �
                                                              ^
SyntaxError: Invalid or unexpected token
    at createScript (vm.js:74:10)
    at Object.runInThisContext (vm.js:116:10)
    at Module._compile (module.js:537:28)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/travis/build/UW-Madison-DoIT/uw-frame/node_modules/less/lib/less/tree/call.js:2:22)

https://travis-ci.org/UW-Madison-DoIT/uw-frame/jobs/264812988#L123-L137

Restarting build to see if that resolves error 🏗️

edit after restart, build passes ✅
it appears error was a fluke.

[vertein]

Running npm version 5.3.0 but was running node version 8 something. An issue search showed that others ran into the same thing. I downgraded my node to a stable version and it looks like it corrected the problem. I pushed a new file that looks better.

Thanks for restarting the job, it was successful. I pushed up the new package-lock file, so I won't merge until the checks run again.

[ChristianMurphy]

LGTM, thanks @vertein!