FAQs
Here are some frequently asked questions about Sodacore and the packages.
What packages and built-in features does Sodacore have?
Sodacore is a collection of packages, that are all maintained under the same repository, and are all published under the @sodacore namespace.
You can find our list of packages here.
How do I get started?
Check out the Getting Started guide to get started with Sodacore.
How do I contribute, request features or report a bug?
Check out the Code of Conduct and then head over to our Community Guide guide to get started.
Why legacy decorators?
When we started building the framework, Bun's support for modern decorators had issues, although after looking through the spec, the new JS decorators have a lot of limitations, i.e. no ability for parameter decorators. We chose to use the legacy decorators as they are more flexible and allow for more complex patterns to be built, we know that at some point, they will be removed, and once that happens, we will probably release a new version of the framework with the new decorators, but until that time, we will continue to use the legacy decorators.
Why did you choose Bun?
Bun feels like a clean, and more modern runtime compared to Node, it has a ton of great features out of the box, and the developer is amazing at getting bugs fixed and releasing new features. Worth noting that most of the Node libraries have been ported over to Bun, so you can still use your favourite libraries, but with a more modern runtime. Also the start speeds... are impressive, even when using it in development mode (i.e. direct TypeScript).
It also solves the ESM/CJS issues, we are fully aware though that not everything will work out of the box, and if that's the case, raise a bug with Bun (if it's bun related) or with us (if it's sodacore related).
Can Dependency Injection names clash?
Yes, they can. If you have two providers with the same name, they will clash and throw an error, we throw an error to try and prevent this, if you're building a library, we suggest you use prefixes to prevent this, i.e. if your plugin is called Magic, then you may call it MagicWandProvider, etc.