lerna link convert

[goto-bus-stop]

This installs dependencies of all packages, the website, and all examples into the root node_modules folder. After an npm install, no further lerna bootstrap is required.

Internal dependencies within the repository now use file: paths. This way npm can do all of it by itself. When doing a lerna publish, lerna temporarily rewrites those to the actual version numbers.

Note that when npm manages all dependencies, devDependencies of subpackages are not installed. This is because the subpackages like @uppy/core are themselves seen as dependencies by npm. dev dependencies need to be added to the root package.json instead. For the examples and the website, I've just moved everything to normal dependencies.

We now have a single package-lock.json containing all dependencies, so we can do npm ci on travis to save some time.

Best to make npm happy by removing all the node_modules folders first:

rm -r node_modules \
    website/node_modules \
    packages/uppy/node_modules \
    packages/@uppy/*/node_modules

The change list here is big because of all the lockfile changes. Almost every change to master will cause merge conflicts, but they are extremely easy to fix so we don't have to rush to get this in.

[arturi]

We should update docs probably, everywhere we say to use bootstrap?

[arturi]

Very nice! Looking forward to not running bootstrap :) Checked dev example, website and some examples locally — all worked.

[goto-bus-stop]

Ahh, think I figured out the CI failure finally.
When you npm install, npm tries to chmod +x any files that are mentioned in bin fields in package.json files. For Companion, that file was lib/standalone/start-server.js. But at the time the first npm install is done, we haven't been able to run build steps, so that file doesn't exist yet. I eventually fixed it by adding a bin/companion file that just require()s the file in lib/.