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

mira-logger-js

v0.1.8

Published

An opinionated logging client for Node and the browser.

Downloads

25

Readme

mira-logger-js

An opinionated logging client for Node and the browser.

Usage

Initializing the client

const { MiraLogger } = require('mira-logger-js');

const logger = new MiraLogger({
  token: env.LOGGLY_CUSTOMER_TOKEN,
  environment: env.ENVIRONMENT,
  revision: env.REVISION,
  service: 'my-service',
});

See MiraLoggerOptions for the full set of options.

Log levels

logger.debug('debug message');
logger.info('info message');
logger.warn('warning message');
logger.error('error message');
logger.error(new Error('error message'));

// Send logs.
await logger.flush();

Setting context (optional)

Set the context to send with each subsequent log.

logger.setContext({ requestId: 'some-uuid' });

...

// Context passed in with an individual log is merged in with
// the default context set with `setContext`.
logger.info('info message', { statusCode: 200 });

// Logs [{ message: 'info message', requestId: 'some-uuid', statusCode: 200 }]
await logger.flush();

See Context for the full set of options.

Wrapping functions

Wrap a function with logger.wrap to automatically log errors and flush on return. Works with async functions too.

logger.wrap(async event => {
  // Thrown errors are automatically logged.
  throw Error('Oops!');

  // logger.flush() is called when this function returns;
  const data = await doStuff();
  return data;
});

Examples

Http Errors

class HttpError extends Error {
  constructor(code, message) {
    super(message);
    this.name = 'HttpError';
    // statusCode will automatically be logged.
    this.statusCode = code;
  }
}

const res = await fetch('https://example.com');

if (!res.ok) {
  logger.error(new HttpError(res.status, res.statusText));
}

Lambda Scheduled Event

const logger = new MiraLogger({
  token: env.LOGGLY_CUSTOMER_TOKEN,
  environment: env.ENVIRONMENT,
  service: 'my-service',
  // We manually flush at the end of the lambda so there's not
  // much point in keeping auto flushing enabled.
  enableAutoFlush: false
});

module.exports.handler = logger.wrap(async event => {
  logger.setContext({
    requestId: event.id,
    source: event.resources.join(','),
  });

  logger.info('Doing stuff...');

  const res = await fetch('https://example.com');
  if (!res.ok) {
    throw new Error(`Failed to fetch: ${res.status} | ${res.statusText}`);
  }

  logger.info('Done doing stuff.');

  ...

  // logger will flush after returning.
  return data
})

Publishing to NPM

Publishing is currently manual. Grab the NPM login from 1password.

  1. Bump the version in package.json.
  2. Run yarn deploy.
  3. Commit with the version name and push (ie. git commit -m "v0.1.5")