fix(proxy-state-tree): fix docs, as bug to test release

Author: christianalfoni

.travis.yml

@@ -38,8 +38,7 @@ after_success:
       npm run release
     fi
     if [[ $TRAVIS_BRANCH == 'master' ]] && [[ $TRAVIS_PULL_REQUEST == 'false' ]]; then
-
-      now ./packages/overmind-website -e REDIRECT_URL=https://overmindjs.org/ now-examples/redirect --docker --token $NOW_TOKEN && now alias www.overmindjs.org --token $NOW_TOKEN
+      now ./packages/overmind-website -e REDIRECT_URL=https://overmindjs.org/ ./packages/overmind-website --docker --token $NOW_TOKEN && now alias www.overmindjs.org --token $NOW_TOKEN
     fi
     if [[ $TRAVIS_BRANCH == 'next' ]] && [[ $TRAVIS_PULL_REQUEST == 'false' ]]; then
       now ./packages/overmind-website --docker --token $NOW_TOKEN && now alias next.overmindjs.org --token $NOW_TOKEN

packages/node_modules/proxy-state-tree/README.md

@@ -1,7 +1,7 @@
 # proxy-state-tree
 An implementation of the Mobx/Vue state tracking approach, for library authors 
 
-`npm install proxy-state-tree@beta`
+`npm install proxy-state-tree`
 
 ## Why
 The **proxy-state-tree** project is created to stimulate innovation in state management. The introduction of [Flux](https://facebook.github.io/flux/) was followed by a big wave of libraries trying to improve on the idea. All these iterations helped moving the community forward and [Redux](https://redux.js.org/) was born a year later. It was frustrating to have all these variations of the same idea, but at the same time it made the core idea better. One factor I believe made this possible is that Flux state management is based on **immutability**. It is a difficult concept to understand, but when you understand it, it is easy to implement the concept of **change**. You literally just check if a value you depend on has changed. That said, immutability tends to put a lof effort on the hands of the consumer. You have to think really hard about how you structure state and expose state to components to avoid performance issues and prevent boilerplate.