Running `yarn run release` causes issues as it can't communicate with
the proper npm registry. This happens because yarn overrides the
`npm_config_registry` variable, on which the publishing depends.
In this commit I revert the value to its default, allowing the release
script to be run either with `npm run release` or `yarn run release`.
* chore(stack update): update the whole docsearch stack
In an effort to reduce our stack diversity I am moving docsearch to:
- latest eslint
- prettier
- webpack 2
- babel 6 (babel 7 is soon to be released, we were on babel 5)
- babel-preset-env (support: IE >=9, Two latest version of evergreen
browsers).
- jest
* chore(contrib): remove develop branch, cc @redox
