Some tweaks and updates (#18)

Author: garyb

.travis.yml

@@ -1,17 +1,17 @@
 language: node_js
-sudo: false
-node_js:
-  - 5
+dist: trusty
+sudo: required
+node_js: 6
 install:
   - npm install -g bower
   - npm install
 script:
-  - npm run test
+  - bower install --production
+  - npm run -s build
+  - bower install
+  - npm -s test
 after_success:
 - >-
   test $TRAVIS_TAG &&
-  psc-publish > .pursuit.json &&
-  curl -X POST http://pursuit.purescript.org/packages \
-    -d @.pursuit.json \
-    -H 'Accept: application/json' \
-    -H "Authorization: token ${GITHUB_TOKEN}"
+  echo $GITHUB_TOKEN | pulp login &&
+  echo y | pulp publish --no-push

README.md

@@ -12,7 +12,7 @@ A type-safe abstraction for platform-independent file system paths.
 fullPath = rootDir </> dir "baz" </> file "foo.png"
 ```
 
-See the [examples file](/examples/src/Examples.purs) for more.
+See the [tests file](/test/Main.purs) for various example usages more.
 
 # Getting Started
 
@@ -28,7 +28,7 @@ import Data.Path.Pathy
 
 ## Introduction
 
-Applications often have to refer to file system paths in a platform-independent way. 
+Applications often have to refer to file system paths in a platform-independent way.
 
 Many path libraries provide a single abstraction to deal with file system paths. This allows easy composition of different kinds of paths, but comes at the expense of the following distinctions:
 
@@ -57,7 +57,7 @@ Building path liberals is easy. You will typically build path literals from the
 For example:
 
 ```purescript
-let 
+let
   path1 = rootDir    </> dir "foo" </> dir "bar" </> file "baz.boo"
   path2 = currentDir </> dir "foo"
 in do
@@ -134,7 +134,7 @@ All the path literals you build by hand are automatically sandboxed, unless you
 
 There are many other functions available to you for renaming files, renaming directories, getting parent directories, etc.
 
-These are all documented in [MODULES.md](MODULES.md), and you can find [examples](/examples/Examples.purs) for most of them.
+These are all documented [on Pursuit](http://pursuit.purescript.org/packages/purescript-pathy), and you can find [test usages](/test/Main.purs) for most of them.
 
 # API Docs
 

bower.json

@@ -23,6 +23,7 @@
     "purescript-profunctor": "^1.0.0",
     "purescript-strings": "^1.0.0",
     "purescript-transformers": "^1.0.0",
-    "purescript-partial": "^1.1.2"
+    "purescript-partial": "^1.1.2",
+    "purescript-unsafe-coerce": "^1.0.0"
   }
 }

package.json

@@ -1,15 +1,14 @@
 {
   "private": true,
   "scripts": {
-    "postinstall": "bower install",
     "clean": "rimraf output && rimraf .pulp-cache",
-    "build": "pulp build",
+    "build": "pulp build --censor-lib --strict",
     "test": "pulp test"
   },
   "devDependencies": {
-    "pulp": "^9.0.1",
+    "pulp": "^9.0.0",
+    "purescript-psa": "^0.3.9",
     "purescript": "^0.9.1",
-    "rimraf": "^2.5.2",
-    "bower": "^1.7.9"
+    "rimraf": "^2.5.0"
   }
 }