DX w/ monorepo tooling

[luixo]

Story

As a developer who just started working on projects, I stumbled upon a bump while bootstrapping the app. The repository seems to be monorepo, but lacks appropriate tooling (e.g. lerna, pnpm). There is no instruction for a developer to run npm i in every folder you're going to work in, and default npm i in root folder didn't help much. Combining with wild-card module declaration (which is in my belief smelly code by itself) it caused me to dig for some time why every module in project is broken and linked to wildcard module declaration.

Proposals

• add monorepo tooling (probably later, it takes more than just a couple of steps)
• add bootstrap instructions in every sub-repo
• be more developer-friendly, even if a developer came from non-nodejs world (to fix something pretty trivial, for example)

[frol]

There are just two subprojects (backend and frontend), so it felt like an overkill to introduce extra tooling for that. My plan was to use docker-compose as the way to document how to run the project altogether.

P.S. cli folder should be removed: https://github.com/near/near-explorer/pull/804

[luixo]

As of my experience, in this kind of setup (just client and server) package.json is usually shared. Anyway, I believe a little extra documentation won't hurt anyone

[frol]

Meh, I don't think it is a good idea to mix client and server dependencies / commands since that may cause various unexpected issues.

P.S. I am all for improvements to documentation :+1:

[luixo]

This might do it.