Automate deploy using Travis

[alexewerlof]

https://docs.travis-ci.com/user/deployment/npm/

[alexewerlof]

I did a little research and it seems Travis doesn't honour the packages in subdirs (ie. it tries to publish the package from the root which is obviously not what we want).
There's a issue/question for that travis-ci/travis-ci#5676 but no answer since last year.

So we have two choices:

1. Forget the monorepo thingie and move eslint-config-schibsted-react to its own repo.
2. Forget the Travis deploy thingie

There might be:

3. If I'm missing something and there actually is a workaround for this limitation? If anyone wants to follow up the research this is how far I've come. Use Lerna #44 Lerna for example?

@SimenB 💭 ?

[SimenB]

My vote is nr 2. Especially if we get lerna up and running, deploying is very easy.

If we don't, I suppose we could split up the repo