The top level package.json is responsible for installing all dependencies. stdlib is unable to handle an npm install that declares git dependencies. Since storj.js has git dependencies, we have to hack together our dependency tree.
In the top level directory, run npm install which will clone our single dep (storj.js) into a directory called ./deps and do and will install all of its dependencies. This directory then will be copied into each of the services directories so they will be uploaded alongside our codebases.
Our tests are integration tests that will run against a real stdlib deployment.
npm test will handle installing all of the test's dependencies and kicking off the test. The tests expect the following environment variables:
STORJ_EMAIL: email address for the storj account we will run the tests againstSTORJ_PASSWORD: password for the storj accountSTDLIB_ENV: What deployment are we targeting? (i.e.devvsrelease)
Before testing, it might be handy to run this quick script to upload all of your recent changes to stdlib's dev environment:
find . -maxdepth 1 -mindepth 1 -type d | grep -v '.git\|deps\|test' | xargs -I{} bash -c 'echo "Uploading {}" && cd {} && lib up dev'
After verifying the tests work in production, you can cut a release.
You can use the same script as above but modified to ship to production:
find . -maxdepth 1 -mindepth 1 -type d | grep -v '.git\|deps\|test' | xargs -I{} bash -c 'echo "Uploading {}" && cd {} && lib up release'
After uploading to production, you can verify the deploy by re-running the tests with STDLIB_ENV=release.