hadron
hadron copied to clipboard
⚛️Framework for building a testable, modular backend with a dependency injection pattern in plain JavaScript.
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.10 to 4.17.15. Commits - [`ddfd9b1`](https://github.com/lodash/lodash/commit/ddfd9b11a0126db2302cb70ec9973b66baec0975) Bump to v4.17.15. - [`b185fce`](https://github.com/lodash/lodash/commit/b185fcee26b2133bd071f4aaca14b455c2ed1008) Rebuild lodash and docs. - [`be87d30`](https://github.com/lodash/lodash/commit/be87d303941222b97c482755afc0f4a77ce46c30) Bump to v4.17.14. - [`a6fe6b1`](https://github.com/lodash/lodash/commit/a6fe6b1e174fd02b5e60eb2664405f4c1262c300) Rebuild lodash and docs. -...
It is impossible to handle the createConnection error due to ``console.error(err)`` which ends the process. In my opinion, there should be a way to handle it outside the Hadron.
I have got few issues with typescript types in Hadron. At first, I get an error related to declaration files. It shows up to every hadron package when trying to...
Hi, how do you advise porting an existing graphql application into Hadron? Hadron sports a structure that I find highly desirable and appropriate for my project.
While using validator, we need to import validatorProvider and then manually call it and register result into container. It should be handled automatically with ```register``` method
Removes express from an application (hadron demo). Instead, it's moved into hadron-express itself. It introduces also sequence for plugin registration.
setting null as a result of the event without callback is dangerous. The user can rely on the event result, therefore, it may break its code.