Package Exports

@hapiness/logger

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@hapiness/logger) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Logger Module

Logger module for the Hapiness framework.

Using your module inside Hapiness application
- Yarn or NPM it in your package.json
- Import LoggerModule from the library
Contributing
Change History
Maintainers
License

Using your module inside Hapiness application

`yarn` or `npm` it in your `package.json`

$ npm install --save @hapiness/core @hapiness/logger rxjs

or

$ yarn add @hapiness/core @hapiness/logger rxjs

"dependencies": {
    "@hapiness/core": "^1.2.2",
    "@hapiness/logger": "^1.1.0",
    "rxjs": "^5.5.2",
    //...
}
//...

import `LoggerModule` from the library

import { Hapiness, HapinessModule, HttpServer, OnGet } from '@hapiness/core';
import { LoggerModule, LoggerService } from '@hapiness/logger';

@HapinessModule({
    version: '1.0.0',
    imports: [
        LoggerModule
    ]
})
class HapinessModuleApp {
    constructor(private _logger: LoggerService) {
        this._logger.info('my data log');
    }
}

@Route({
    method: 'get',
    path: '/test'
})
class MyRoute implements OnGet {
    constructor(private _logger: LoggerService) {}
    onGet(request, reply) {
        this._logger.warn('my data log');
        reply('test');
    }
}

// Define your logger

Hapiness.bootstrap(HapinessModuleApp, [ LoggerExt.setConfig({ logger: myLogger }) ]);

Access logs

If HttpServerExt is loaded, the LoggerModule will inject an AccessLogs component. To desactivate the access logs, provide a module's config:

@HapinessModule({
    version: '1.0.0',
    imports: [
        LoggerModule.setConfig({ accessLogs: false })
    ]
})
class HapinessModuleApp {
    ...
}

Contributing

To set up your development environment:

clone the repo to your workspace,
in the shell cd to the main folder,
hit npm or yarn install,
run npm or yarn run test.
- It will lint the code and execute all tests.
- The test coverage report can be viewed from ./coverage/lcov-report/index.html.

Change History

v1.1.0 (2017-11-20)
- Latest packages' versions.
- Documentation.
- Change packaging process.
v1.0.0 (2017-10-26)
- Create LoggerModule
- Logger extension
- Logger provider
- Access logs
- Documentation

Maintainers



Julien Fauville	Antoine Gomez	Sébastien Ritz	Nicolas Jessel

@hapiness/logger