update lerna to version 3.x and change readme and corresponding packa…

…ge.json commands accordingly

README.md

@@ -465,7 +465,8 @@ You can use the wrapper `serve-dev` to run the whole development setup, but note
 2. `node scripts/build` can't use npm run or lerna run because rollup can't handle non-externalized dependencies when lerna is symlinking them.
 3. `node scripts/publish` this doesn't actually publish yet, but copies the transpiled output from `packages/*/build/` to the top-level `dist/` directory.
 4. git `add` and `commit`
-5. `lerna publish`   choose version numbers for each changed package
+5. `lerna version` to choose version numbers for each changed package.
+6. `lerna publish` to publish to the NPM repository.
 
 This publishes to npm as well as creates new git tags for the releases, which are pushed to Github. To finish the release, go to the  Github repo's release page and annotate the latest release for the 'nlmaps' package (this makes it show up under the 'latest' path on Github).
 

package.json

@@ -6,8 +6,7 @@
   "jsnext:main": "dist/nlmaps.es.js",
   "scripts": {
     "bootstrap": "lerna bootstrap",
-    "lernapublish": "lerna publish --skip-git --skip-npm --repo-version $npm_package_version --yes",
-    "test": "echo \"Error: no test specified\" && exit 1",
+    "lernapublish": "lerna version $npm_package_version --no-git-tag-version --no-push --yes",
     "build": "echo \"Use node scripts/build.js instead\"",
     "serve": "node scripts/serve.js",
     "watch": "echo \"Use node scripts/build.js --watch instead\""
@@ -26,7 +25,7 @@
     "buffertools": "^2.1.6",
     "eslint": "^4.19.1",
     "leaflet-headless": "^0.2.6",
-    "lerna": "^2.11.0",
+    "lerna": "^3.22.1",
     "live-server": "^1.2.0",
     "live-server-https": "0.0.2",
     "nodemon": "^1.18.3",