[Feature]: Create starter/example-repos that show how to use inversify in a larger use case

[Floriferous]

🚀 Feature Proposal

There are very little examples for how to best organize a codebase with inversify, leaving a lot of boilerplate up to the user.

I think the docs would really benefit from having more patterns that seem a bit more real and useful than katanas and ninjas. On top of that, having an "example" folder here that has a few sample apps that use inversify as it was meant to be used to quickly understand the right patterns.

Motivation

It is not always obvious how to best use the features inversify has to offer, or how to structure a code base properly as it scales up.

Example

No response

Pitch

I'm sure the maintainers here, or some other users figured it all out, and so vibe coding a few examples may not take that much time, but could really help with adoption.

Could even have some boilerplate generator stuff like:
npx inversify create --express or npx inversify create --hono

[notaphplover]

There are very little examples for how to best organize a codebase with inversify, leaving a lot of boilerplate up to the user.

I believe in giving freedom to users to take the approach they prefer most. Organizing the codebase depends on the nature of the project: a backend package of a monorepo in the context of a mature and already profitable project needs to rely on different patterns than a single web page application being built by the developer team of a startup.

We have the examples repo with more complex examples. I think we can add some README.md files in each example and link them in the docs. Would that be helpful to you?

Could even have some boilerplate generator stuff like:
npx inversify create --express or npx inversify create --hono.

Yeah, we could probably do that, but, as said, it would be an example of how to setup a basic express / hono bakend. Let's say we go for it, and we provide a heroes dummy CRUD. Should we use a layered architecture? For the sake of clarity, I believe we should not. But some projects should indeed use a layered architecture if the trade of happens to be positive.

Having said that, I agree it would help with adoption, I'll keep the issue open so the generator utils can be implemented 🙂.

[Floriferous]

Yeah I agree everyone should have the freedom to do what they want, but figuring out idiomatic and scaleable setups has not been trivial (for me at least). It would've helped me to see a few sample repos for how to organize various applications.

I found examples in packages/container/examples, not sure if that's what you're talking about? In any case they're like a dozen lines of code, which is not super helpful beyond what the docs already offer.

I really think onboarding into these libraries and frameworks is not easy at the moment :)

[notaphplover]

Yeah I agree everyone should have the freedom to do what they want, but figuring out idiomatic and scaleable setups has not been trivial (for me at least). It would've helped me to see a few sample repos for how to organize various applications.

I think I can do that, yeah.

I found examples in packages/container/examples, not sure if that's what you're talking about? In any case they're like a dozen lines of code, which is not super helpful beyond what the docs already offer.

My bad, wrong link. I fixed it. The repo is at https://github.com/inversify/framework-examples. It shows some more complex examples. We could probably add some pages with common architectural patterns.

I really think onboarding into these libraries and frameworks is not easy at the moment :)

Then please consider having a look at https://github.com/inversify/framework-examples. If those samples are helpful, let's think the best way to showcase common architectural patterns to fellow devs 🙂