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

@atos6/serverless-utils

v0.0.1-beta

Published

This packages will help out with our lambdas, with shared code between then.

Downloads

5

Readme

serverless-utils

This packages will help out with our lambdas, with shared code between then.

Features

  • Logger

| Parameter name | Description | | ---------------- | ------------ | | service | The service name which the logger is being reporting, it is useful when our lambda logger move to a centralized logger | | format | Default: 'json', will print the log as json format, available options are: ['json', 'plain']. Plain will print directly to the console as normal text |

Example:

import { Logger } from '@raise-sistemas/serverless-utils'

const logger = new Logger({ service: 'PAYMENTS' })

const transaction = {
  id: '123'
}

logger.info(`Payment transaction create with ${transaction.id}`)

The logger above will print as json (as defined by default) as:

{
  "service": "PAYMENTS",
  "message": "Payment transaction create with 123",
  "data": {}
}

Or if the plain format is choosen:

[PAYMENTS]: 'Payment transaction create with 123'

The last data field on json format is filled if instead of passing the above logger.info, passing an additional parameters to the logger, see below:

logger.info(`Payment transaction create with ${transaction.id}`, transaction)

PS: Might be useful to debug and see what kind of data raises a logger message.

{
  "service": "PAYMENTS",
  "message": "Payment transaction create with 123",
  "data": {
    "id": "123"
  }
}

The log levels defined are: 'info', 'warn', 'error' and 'debug'

logger.info(`Payment transaction create with ${transaction.id}`, transaction)
logger.warn(`Payment transaction create with ${transaction.id}`, transaction)
logger.error(`Payment transaction create with ${transaction.id}`, transaction)
logger.debug(`Payment transaction create with ${transaction.id}`, transaction)
  • Response

This has an only one function for now called create:

import { Response } from '@raise-sistemas/serverless-utils'

Response.create(422, { 'error': 'payment_transaction_invalid' })

It's useful with aws lambda response to finish a call through API Gateway