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

@atp-autoteile/logger

v0.0.15

Published

Library, created for logging errors using Sentry

Downloads

5,230

Readme

ATP_Logger

Library, created for logging errors using Sentry

! IMPORTANT !

  • Library requires ATP_LOGGER_DSN env variable to log Sentry errors

  • ATP_LOGGER_ENV is required for specific Sentry environment ('production' by default)

  • APPLICATIONINSIGHTS_CONNECTION_STRING is required for Azure Application Insights service

  • run npm version <version_name> after every update

USAGE

Logger has 4 levels of logging

debug info warn error

Simply import the Logger and call info method to log a message:

import { Logger } from '@atp-autoteile/logger'

const logger = new Logger('service name')
logger.info<string>('Info message')

// loggig errors
try {
  throw new Error('Your custom message...'); 
}
catch (err) {
  logger.error(err);
}

For CommonJS module:

const { Logger } = require('@atp-autoteile/logger')

const logger = new Logger('service name')
logger.info('Info message')

Set a service name as a parameter for constructor when creating new Logger instance if you want to use custom log message prefix. Default value is 'ATP_Logger'

env parameters example:

ATP_LOGGER_DSN='https://******@sentry.io/12345'
ATP_LOGGER_ENV='staging'
APPLICATIONINSIGHTS_CONNECTION_STRING='InstrumentationKey=******;IngestionEndpoint=https://******.in.applicationinsights.azure.com/;LiveEndpoint=https://eastus.livediagnostics.monitor.azure.com/'