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

@omnicar/sam-log

v1.2.2

Published

Handles logging to console and to stackdriver

Downloads

112

Readme

SAM-log

Usage

The default settings should make sure that no initialisation of the library is needed for Omnicar's applications. The only prerequisite to having the library default to sane environment specific loglevels is having the NODE_ENV environment variable available (set to: production | staging | development | local)

Another option is to have the LOG_LEVEL environment variable available (has to be one of: error | warn | info | verbose | debug | silly) which will set/override the loglevel directly

To use the library, simply import the log function needed. E.g. logError and use it like a regular call to console.error

It's possible to use an optional prefix for all the logging methods. The available logging methods are:

  • logError(message: string | object, info?: ILogInfo)
  • logWarn(message: string | object, info?: ILogInfo)
  • logInfo(message: string | object, info?: ILogInfo)
  • logVerbose(message: string | object, info?: ILogInfo)
  • logDebug(message: string | object, info?: ILogInfo)

Developing

Pull the project, run yarn and you should be good

Before you do a git push, please run yarn tsc-once to generate the build folder contents

Testing

There are a bunch of jest tests in the index.test.ts file. Run yarn test to run all tests, yarn test-watch to run them in watch-mode, and run yarn test-debug to run them in watch mode with --inspect enabled (allowing you to step debug)

Releasing

Releasing a new version is done as a Github release.

The Github release will automatically trigger a build in Circle that publishes the new version to npm 👍