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

@wymp/weenie-service-manager

v1.3.0

Published

This is the service manager package for Weenie, an unopinionated Typescript microservice framework.

Downloads

29

Readme

Weenie Service Manager

This package is meant to be used with Weenie. However, if you are not using Weenie but are interested in this functionality, there's nothing wrong with using it directly.

Functionality

The main export of this library is the serviceManager function, which returns a svc dependency with three properties: whenReady: Promise<void>, declareReady: () => void and onShutdown: (task: () => Promise<void>) => void. See src/serviceManager.ts for more detailed documentation.

  • Startup monitoring - Sets a timeout (configurable with config.svc.initializationTimeoutMs) that kills the process if the svc.declareReady() function is not called within the configured time. When svc.declareReady() is called, the svc.whenReady promise is resolved, allowing dependents to activate functionality when all dependencies are known to be ready.
  • Shutdown management - If configured to do so (with config.svc.handleShutdown), registers event listeners on SIGINT and SIGTERM signals and runs any shutdown tasks prior to exiting the process. Shutdown tasks may be registered by passing a function returning a promise to the svc.onShutdown() function. For example, you may want to close your database cleanly on shutdown, so you might pass svc.onShutdown(() => db.close()). (Note: this shutdown functionality is also accessible to the running application via the svc.shutdown() function.)

Config

See src/serviceManager.ts for config options. (If you use a modern editor like vscode, the documentation should pop up on mouse-over.)

Example

import { Weenie, logger, serviceManager } from '@wymp/weenie-framework';

const config = {
  logger: {
    logLevel: 'notice',
  },
  svc: {
    initializationTimeoutMs: 10_000,
    handleShutdown: true,
  },
}

const deps = Weenie({ config })
  .and(logger)
  .and(serviceManager)
  .done((d) => d);

// Do other setup ....
deps.svc.whenReady.then(() => deps.log.notice(`Service started!`));
deps.svc.onShutdown(async () => { deps.log.notice(`Service shutting down`) });

// Now let everything know the service is ready to start
deps.svc.declareReady();