Repo structure about threeify

[bhouston]

Can we could also likely make the threeify-glsl-transpiler a module in the same spirit. I do like that structure. Let's do it.

[bhouston]

We could just adopt Yarn2 instead of Lerna. I understand this is preferred.

A popular recipe for setting up monorepo for JavScript projects is the combination of Yarn’s workspaces (existed since Yarn 1) and Lerna as a project manager.

The good news with Yarn 2 is that now, Yarn doubles as being both a package manager as well as a project manager and aims to provide a wholesome experience for running monorepos smoothly.

https://snyk.io/blog/yarn-2-intro/

More details:

https://dev.to/lampewebdev/node-on-rails-creating-a-monorepo-aka-workspaces-with-yarn-284i

[bhouston]

I've asked for input on Twitter here: https://twitter.com/BenHouston3D/status/1270750233316798467

[Astrak]

Yes I wanted to make a case for yarn for another reason, but it's a better tool indeed

[Astrak]

Lena works with yarn workspaces also, so we can use both together

[bhouston]

Internally we are just using Yarn2. My recommendation is to lets get this working as a rendering engine before going modular. I just want to ensure that we can get provable results from the project before refactoring it.

[bhouston]

BTW I was able to get "@threeify/" modules resolution working in the /examples folder via just tsconfig.json settings. Using this approach:

https://stackoverflow.com/a/43330003

[bhouston]

I've adopted a mono-repository format.