Improve management of multiple javascript projects in the repo

[mnaamani]

We should be using yarn workspaces to manage our multiple javascript projects, as well as lerna tools https://github.com/lerna/lerna

Reconsider the organisation of network tests, cli, query-node to fit in this model.

[bedeho]

What is the TLDR on the benefits of this?

[mnaamani]

The point about workspaces is primarily to make packages from one project/app re-usable by others without need to publish a pacakge to npm or while locally developing using yarn add localpath tricks.

lerna I think will be required to help publish to npm packages in a more practical way. Currently I have to change into the directory of the module and npm publish.

Hopefully using lerna it will also solve an inconsistency which we currently have with the @joystream/types package. The way it is built and consumed by packages in the same workspace is different than how you consume it when you us the npm published version.

I'm speaking specifically about the need to add the /lib/ in the import path.

// inside pioneer worksapce
import { ChannelId } from '@joystream/types/content-working-group';

// in storage-node for example
import { ChannelId } from '@joystream/types/lib/content-working-group';

I think re-organizing the projects folder structure might be pushing it and likely not necessary, as @Lezek123 is discovering while importing pioneer into the monorepo.

There are other issues he is getting into but I'm sure he will figure them out.

[mnaamani]

Related: #402