Outsource Collection into a separate package

[bennobuilder]

🆕 Feature Request

❓ Is your feature request related to a problem?

Big bundle size 🐘

📄 Describe the solution you'd like

I would like to install the Collection as a separate package when I really need it.

📃 Describe alternatives you've considered

Life with a larger bundle size, although I don't need the Collection feature.

[bennobuilder]

🟩 Pros

• smaller bundle size
• more encapsulation

🟥 Cons

• No Collection type safety in integrations like React (useAgile())
• No way to offer a type safe App.createCollection()

[bennobuilder]

https://github.com/agile-ts/agile/tree/experimental-outsource-collection

[bennobuilder]

Problems with optional types:

• https://stackoverflow.com/questions/54392809/how-do-i-handle-optional-peer-dependencies-when-publishing-a-typescript-package

• https://stackoverflow.com/questions/52795354/how-to-use-a-type-from-an-optional-dependency-in-a-declaration-file

[bennobuilder]

Still considerable, but for now the Collection can be tree shaken away
See: #186