npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mimik/init

v5.3.0

Published

Init process for micro-service

Downloads

169

Readme

init

Example

const init = require('@mimik/init');

init(config, dbValidate, { postOps: [suscribe] }).then(result => config = result);

module.exports(app, rootDir, config, validates, cluster, options) ⇒ object

Init process for a micro-service.

Kind: Exported function
Returns: object - The updated configuration.

The secOptions has the following structure:

 {
   preOps: [function], // functions to process before starting the micro-service
   postOps: [function], // functions to process after starting the micro-service
   exitOps: [function], // functions to process before exiting the micro-service
   secOptions: { securityDefinition: function }, // extra security options to validate the API request
   extractName: string, // ability to extract data from the req and send it to a logging environment
   metrics: object, // to genetrate information for `/metrics`
 }

The return object has the following strucuture:

 {
   config: The configuration object,
 }

For the preOps, postOps and exitOps the function are executed with 3 parameters (correlationId, config, server). The following routes are reserved: /healthcheck and /metrics. The base path is defined by taking the url property of the first item of the servers array in the api defintion file. Only relative url address will be handled (e.g. /mss/v1) and templates in the url are not allowed.

| Param | Type | Description | | --- | --- | --- | | app | object | The app implementing the micro-service. | | rootDir | PATH.<string> | The root directory of the micro-service. | | config | object | Configuration of the micro-service. | | validates | array | Array of Promises to validate dependent systems (database, topic). | | cluster | Promise | Promise to be used for cluster management and registration. | | options | object | options to start the micro-service. The options can be null. |