Issue329 node 12

[jspaaks]

fixes #329

[jspaaks]

For some reason, the order of some elements has changed and as a result the admin tests on travis fail because some parts of the snapshots are different than what is being generated.

in part this could be due to some elements in the admin interface having been assigned an equal value for sortIndex, e.g.

research-software-directory/admin/public/settings.json

Lines 49 to 65 in 5af4032

	"sortIndex": 500,
	"help":
	"The <a href=\"https://help.zenodo.org/#versioning\">Zenodo concept DOI</a>. Not a URL"
	},
	"createdAt": {
	"label": "Created at",
	"sortIndex": 1000,
	"readonly": true
	},
	"createdBy": {
	"label": "Created by",
	"sortIndex": 1000,
	"readonly": true
	},
	"getStartedURL": {
	"label": "Getting started URL",
	"sortIndex": 500

This however does not explain the changed order of some of the other elements, e.g. the mentions Maybe related, when building the admin, I got a previously unseen error

warning sha.js@2.4.11: Invalid bin entry for "sha.js" (in "sha.js").

[jspaaks]

Related:

• add notes on how to update the jest snapshots that are used for regression testing of /admin #321
• Upgrade Node.js 8 in admin #329
• fix: yarn warning for invalid bin entry browserify/sha.js#65
• Allow dots in bin names yarnpkg/yarn#7811

[sverhoeven]

The order must be due to the Node version iterating through the properties in a different way.

[sverhoeven]

Tried branch and was also able to use the admin interface