Every solution should include comprehensive documentation, which explains at least:
- Why there is a need in this solution. A couple of use cases.
- How to use this solution. A couple of code samples.
- Is there any limitations now or in the future we need to know about before using it.
| Name | Status | Description |
|---|---|---|
| JS Style |  |
Javascript style conventions |
| Node.JS conventions | |
Node.JS, package.json conventions |
| PDF generation service | |
Service that allow generate PDF documents from html files |
| Name | Status | Description | Distribution |
|---|---|---|---|
| Handy MongoDB layer | |
Handy MongoDB layer with database transaction log capabilities | npm package: @paralect/mongo-node8 |
| Config management | |
Describe a common way and show example of managing configs for different environments | source code |
| Common logger | |
Should support logging to the File, Logstash, Loggly | npm package: @paralect/common-logger |
| Name | Status | Description | Distribution |
|---|---|---|---|
| Koa.JS React.JS starter app | |
A simplest way to start your Koa/React.JS based app. | source code |
| Koa.JS 2 api application starter | |
Simple API starter that already have logging, connection to MongoDB and sample resource implementation | source code |