Move to a monorepo

[brianmhunt]

I had separated out the KO scripts into packages to make absolutely certain that the relationships between the packages was logical and minimal (i.e. I couldn't make lazy cross-references 😉 ).

Now that we've got a fairly logical ES6 hierarchy, and I think the essential build tools are set, it might be time to bring it all together.

The most common way to combine multiple packages like this appears to be a monorepo with lerna.

Never having gone down the monorepo path, I have some skepticism, but it's evidently got quite a lot of mindshare.

I wanted to post this issue for two reasons:

1. Invite any feedback – any experience with the monorepo design/tools (e.g. lerna); and
2. So nobody wonders all the repos are being deleted.

Any thoughts: @knockout/core @knockout/extended

Cheers 🍻

[mbest]

I'm in favor of a monorepo. I tried working with the tko repositories and found it quite cumbersome (and resource heavy).

[brianmhunt]

To try and preserve as much history from the other repositories as possible, as part of this move I (effectively) rebased to a new/orphan branch master.

Some action will be necessary to pull/push new changes as expected. The easiest is re-cloning git@github.com:knockout/tko, otherwise it's a bit of mucking around.

Sorry for the inconvenience.

[brianmhunt]

This is complete now, all tests passing.