@rokkit.ts/core NPM

Rokkit.ts Core

GitHub npm (scoped)

Rokkit.ts a microservice framework build in TypeScript for Node.js. It focuses on a modular component system, developer exerience and good designed APIs to build any application without making restrictions.
Rokkit.ts tries to be adaptable for all needs. If you want to know more about the framework check out our Website.
The Framework is still in an early phase but allready provides functionality to build basic applications.

This is the core module of the Rokkit.ts Framwork, it enable the dependency injection for user components and handles other found Rokkit.ts modules on the project. The core module is just the entry point into the Rokkit.ts environment.

Install

Install rokkit.ts as an npm package:

npm install @rokkit.ts/core

Rokkit-CLI

Create your first Rokkit.ts project with the rookit-cli. The cli helps you to bootstrap your project and create a lightweight template to start the development.

npx -p @rokkit.ts/core rokkit-cli init -n <your-project-name>

You can easily build your app using the rokkit-cli. it automates all needed steps and you can just run the app afterwards.

# Projects created with rokkit-cli
npm run build

# Projects created manually
npx rokkit-cli build

Run your app in development or production mode with the cli. You have to specify the entrypoint in order to start the app. Therefore use the parameter -e followed by the path to your root class.

# Development mode
npm run start-dev # Projects created with rokkit-cli
npx rokkit-cli start -e ./src/app.ts

# Production mode
npm start # Projects created with rokkit-cli
npx rokkit-cli start -e ./build/app.js -p

Getting Started

In order to start your first project check out the Getting Started section on our website and try out our cli to create your first project. For a detailed example have a look at our sample application repository.

API

The core module expose only two major functionalities by now:

The entrypoint to start the framework
Dependency Injection utilities

Both will be explained in the following.

The Entrypoint

The entrypoint to the framework is a simple class that would be used to configure and run the framework. Therefore Rokkit exposes a simple API to configure its modules. To configure a module you have two options. The first option would be to use the default configuration provided by Rokkit.ts. The second solution is to define your own configuration object. Rokkit exports there needed type definition that you would need to provide.

The last step next to the configuration of the module would be to run the framework. you can simply call the method run at the end of the call!

import { RokkitRunner, Rokkit, RokkitModules } from  "@rokkit.ts/core"

@RokkitRunner
export class SampleApplication {
  constructor{
    Rokkit.useModule(RokkitModules.WEB)
      .useDefaultConfiguration()
      .run()
  }
}

Dependency Injection Utilities

In order to use or apply dependency injection the core module provides further annotations. Currently there are three different decorator you could use. Let's have a look a the example below to understand the usage.

import { Component, Service, Inject } from  "@rokkit.ts/core"

export class SimpleClass{

}

@Component()
export class SampleComponent{
}

@Service()
export class SampleService {
  constructor(sampleComponent: SampleComponent,
              @Inject(new SimpleClass()) simpleClass: SimpleClass)
}

The example shows the different usecase of the dependency injection decorators. First lets start with the SimpleClass, this class is not marked with any decorator and therefore not recognized by the dependency injection of Rokkit.ts.
Rokkit.ts core module will only search for classes with the decorators @Component or @Service. Each class annotated with one of these is able to be automatically injected into another class because Rokkit.ts will create an injection definition and a related instance on start up. As you can see at the SampleService the constructor contains two parameters. The first one is an object of the SampleComponent, this object will be injected at start up.
You do not need to provide more information at this point the core module is able to determine that this object is an injectable component. The second parameter is an object with the type SimpleClass, because the class is not annotated the core does not know how to inject the object (create an instance of it).
But we can tell the framework to how to do this by using @Inject. This decorator will injection the provided value to the exact parameter we you used it.