npm package: @injectable/core
Description: Minimalistic NodeJS Backend Framework
Author: Bela Bohlender
Latest version: 2.0.13

# Injectable Core

## Minimalistic NodeJS Backend Framework

The goal is to build a framework for reusable services (**Injectables**) in NodeJS.  
Everybody can use and provide such **Injectables** via the node package manager (NPM).
Using RxJS for dynamic values like the state and the configuration.

## Motivation

I love npm with its library versatility and all the support from the community.  
So I wanted to enhance some of these building blocks to lego bricks which just clip together without any glue.  
Obviously you cant do everything with lego bricks because their types are limited but if you can 3d print your own lego bricks, **everything is possible**.

## Concepts

1. **Lifecycle**  
   Each **Injectable** has a lifecycle.  
   It begins with getting loaded and being in the **stopped** state. It stays that way until it gets started which will either lead to the **missing depdencies** or **preparing** state. The **preparing** state gives the **Injectable** the chance to execute things which it needs while running. After finishing these things the **Injectable** will confirm that its ready by setting its state to **running**.

2. **Resources**  
   Having resources between dynamic **Injectables** can lead to unused resources or dead callbacks. So it is key to always clean resources after stopping an **Injectable**. When an **Injectable** dies every depdency gets notified with the `removeResources(injectableName)` function.

3. **Depdencies**  
   Every **Injectable** can have depencies or get required as a depency.  
   **Abstract Depencies** allow multiple solutions for a predefined task.
   For example logging can be done by showing the message in the console or writing it to a file. Either way the core funtion is `log("Hallo Welt")`.

4. **Dynamic**  
   **Injectables** can be loaded or unloaded dynamically.  
   Exchanging **Injectables** dynamically can be done by starting and stopping a **Injectable** while running the system.

5. **Direct**  
   Executing a function from another **Injectable** is done like expected because both programms run in the same process.

## Tutorials

* [Server Tutorial](https://github.com/signinit/injectable-server-tutorial)
* [Injectable Development Tutorial](https://github.com/signinit/injectable-development-tutorial)

## Existing Injectables

* [Log Service](https://github.com/signinit/injectable-log-service)
* [Console Log Service](https://github.com/signinit/injectable-console-log-service)
* [Exporess Service](https://github.com/signinit/injectable-express-service)
* [File Hosting Service](https://github.com/signinit/injectable-file-hosting-service)
* [Webpack Service](https://github.com/signinit/injectable-webpack-service)
* [Server Side Rendering Service](https://github.com/signinit/injectable-server-side-rendering-service)
* [React Service](https://github.com/signinit/injectable-react-service)

If you have developmed an **Injectable** that should be mentioned here please message me.

## License

See the [LICENSE](LICENSE.md) file for license rights and limitations (MIT).