Updated vanilla to 1.5.0 from npm and rebuilt vanilla css files

[bartaz]

Done

Updates Vanilla to 1.5.0 from NPM.
Also updated CSS built from vanilla.

QA

• Check out this feature branch
• Run npm i (to update local npm modules)
• vanilla-framework 1.5.0 should be installed
• Run the site using the command npm start -- --env=environments/dev.env
• View the site locally in your web browser at: http://0.0.0.0:8000/
• Go to a page with breadcrumb (for example build details page)
• Breadcrumb should have new vanilla styles (with blue links)

Issue / Card

Fixes #940

Screenshots

[bartaz]

Breadcrumb pattern was changed and now relies on %clearfix but doesn't import it on its own.

[nottrobin]

Works exactly as described, but I have one change request about version specificity in package.json

[nottrobin]

I'd only be comfortable with using this fuzzy versioning if we have a lockfile. I believe we're using NPM, rather than Yarn, for this project - is that right? In which case the lock-file to use would be package-lock.json. So could we either:

• commit a package-lock.json file and make sure that the build job is using NPM>=5; or
• lock all the dependencies in this file at specific versions

(Hopefully Yarn will one day come to its senses and start supporting package-lock.json)

[nottrobin]

Oh wait - it looks like we use npm-shrinkwrap to solve this problem. That's fine, but it means you need to be committing an update to the npm-shrinkwrap.json file.

[bartaz]

@nottrobin I guess vanilla-framework didn't get into npm-shrinkwrap.json because it's a dev dependency (and dev dependencies are not locked in npm-shrinkwrap).

So if we want vanilla locked - and I agree it would be a good idea, we should move it to regular dependencies, so they will appear in npm-shrinkwrap.

[nottrobin]

@bartaz yes I agree. Given that this site is never going to be an NPM package, the difference between dependencies and devdependencies is academic. So let's add it to regular deps.

[nottrobin]

@bartaz with those changed it LGTM 👍