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

imago-job-logger

v1.1.0

Published

Creates a simple filesystem log.

Downloads

2

Readme

A simple filesystem logger to record a long-running job and serve its status via a Web API.

It exports two classes: JobLogger which saves information to a file, and JobStatusCheck which serves log contents via a Web API.

Prerequisites

  • Create a logs/jobs/ folder in the app service's wwwroot folder.
  • Node 8.9 or above.

Usage

Log information

The log() function is asynchronous. You don't have to await it (to save time), but then the order of log messages is not guaranteed.

Each log must end with the magic string -- All done! -- (stored in the JOB_DONE_MAGIC_STRING), otherwise the .done variable in the response will be false and the frontend wouldn't know when to stop polling the endpoint.

const guid = require('node-uuid');
const { JobLogger, JOB_DONE_MAGIC_STRING } = require('imago-job-logger');

let jobId = guid();

let logger = new JobLogger(this.jobId);

await logger.log('Old app did not exist, so nothing to delete.');
await logger.log(JOB_DONE_MAGIC_STRING); // -- All done! --

Serve log contents to frontend

We assume that the frontend will call this endpoint regularly (for example, each second) and will stop calling the endpoint when response.done is true.

Code inside a route:

const express = require('express');
const { JobStatusCheck } = require('imago-job-logger');

const router = express.Router();

// For the frontend to read the job log of the import job while it is being
// executed:
router.get('/job-status', async (request, response) => {
  new JobStatusCheck().process(request, response);
});

Sample response

There are three variables in the response. success means that the log was found successfully, done means that the job that is being logged has completed, and log contains the log itself.

{
	"success": true,
	"done": true,
	"log": "Old app did not exist, so nothing to delete.
	-- All done! --"
}