Add docs and fix scripts

Author: bigmontz

README.md

@@ -480,8 +480,7 @@ var driver = neo4j.driver(
 ## Building
 
 ```
-./buildDependencies.sh
-npm install
+npm ci
 npm run build
 ```
 

buildDependencies.sh

@@ -7,8 +7,12 @@
   "scripts": {
     "clean": "lerna clean -y && lerna run clean",
     "build": "lerna bootstrap --ci",
-    "test::unit": "lerna run test::unit",
-    "test::integration": "lerna run test::integration",
-    "test::stress": "lerna run test::stress"
+    "test::unit": "lerna run test::unit --stream",
+    "test::integration": "lerna run test::integration --stream",
+    "test::stress": "lerna run test::stress  --stream",
+    "test": "lerna run test --stream",
+    "start-neo4j": "lerna run start-neo4j --scope neo4j-driver",
+    "stop-neo4j": "lerna run stop-neo4j --scope neo4j-driver",
+    "lerna": "lerna"
   }
 }

package.json

@@ -6,18 +6,28 @@ This is an internal package shared by the [neo4j-driver](https://www.npmjs.com/p
 
 ## Building
 
-It's required to first build the `neo4j-driver-core` under the `../core` (see instruction on its folder). Then,
+The build of this package is handled by the root package of this repository.
+
+First it is needed to install the mono-repo dependencies by running `npm ci` in the root of the repository. Then:
+
+* Build all could be performed with 
+
 
 ```
-npm install
 npm run build
+```
+* Build only the Core could be performed with
+Builind only Core:
+```
+npm run build -- --scope=neo4j-driver-bolt-connection
+
 ```
 
 This produces a Node.js module version under `lib/`.
 
 ## Testing
 
-The tests can be executed by running `npm test`. For development, you can have the build tool rerun the tests each time you change the source code:
+The tests could be executed by running `npm test` in this package folder. For development, you can have the build tool rerun the tests each time you change the source code:
 
 ```
 npm run test::watch

packages/bolt-connection/README.md

@@ -6,16 +6,28 @@ This is a internal package shared by the [neo4j-driver](https://www.npmjs.com/pa
 
 ## Building
 
+The build of this package is handled by the root package of this repository.
+
+First it is needed to install the mono-repo dependencies by running `npm ci` in the root of the repository. Then:
+
+* Build all could be performed with 
+
+
 ```
-npm install
 npm run build
+```
+* Build only the Core could be performed with
+Builind only Core:
+```
+npm run build -- --scope=neo4j-driver-core
+
 ```
 
 This produces a Node.js module version under `lib/`.
 
 ## Testing
 
-The tests could be executed by running `npm test`. For development, you can have the build tool rerun the tests each time you change the source code:
+The tests could be executed by running `npm test` in this package folder. For development, you can have the build tool rerun the tests each time you change the source code:
 
 ```
 npm run test::watch

packages/core/README.md

@@ -355,11 +355,20 @@ var driver = neo4j.driver(
 
 ## Building
 
+The build of this package is handled by the root package of this repository.
+
+First it is needed to install the mono-repo dependencies by running `npm ci` in the root of the repository. Then:
+
+* Build all could be performed with 
+
 ```
-./buildDependencies.sh
-npm install
 npm run build
-npn rub build:browser
+```
+* Build only the Core could be performed with
+Builind only Core:
+```
+npm run build -- --scope=neo4j-driver-lite
+
 ```
 
 This produces browser-compatible standalone files under `lib/browser` and a Node.js module version under `lib/`.
@@ -399,14 +408,12 @@ python3 main.py
 
 More details about how to use Teskit could be found on [its repository](https://github.com/neo4j-drivers/testkit/tree/4.3)
 
-Simple `npm test` can also be used if you want to run only the unit tests.
+Runing `npm test` in this package directory can also be used if you want to run only the unit tests.
 
 For development, you can have the build tool rerun the tests each time you change the source code:
 
 ```
 npm run test:watch
 ```
 
-The guides about how to test the driver internal dependencies should be found on it own Readme files.
-
-See `../core` and `../bolt-connection`
+The command `npm run test::unit` could be used in the root package for running the unit tests for all the packages in this project.

packages/neo4j-driver-lite/README.md

@@ -1,14 +1,7 @@
 npm install -g gulp typescript jest
 
-npm --prefix core ci
-npm --prefix core run build
-npm --prefix bolt-connection ci
-npm --prefix bolt-connection run build
-
 npm ci
-
-npm --prefix core test
-npm --prefix bolt-connection test
+npm run build -- --no-private
 
 $ErrorFound = $False
 
@@ -26,7 +19,7 @@ try
 		exit 1
 	}
 
-	npm test
+	npm test -- --no-private
 	if($LastExitCode -ne 0) #failed to execute npm test without error
 	{
 		$ErrorFound = $True

runTests.ps1

@@ -7,15 +7,11 @@ trap finish EXIT
 
 npm install -g gulp typescript jest
 
-./buildDependencies.sh
-
 npm ci
+npm run build -- --no-private
 
 if [[ ! -z "$1" ]]; then
   export NEOCTRL_ARGS="$1"
 fi
 
-npm --prefix ./core/ test
-npm --prefix ./bolt-connection/ test
-
-npm run start-neo4j && npm test
+npm run start-neo4j && npm test -- --no-private