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

@architect/logs

v5.0.5

Published

Manage logging from Architect-provisioned cloud functions

Downloads

14,276

Readme

@architect/logs GitHub CI status

@architect/logs is a module that retrieves and clears logs associated to your @architect functions across environments.

Installation

npm i @architect/logs
let logs = require('@architect/logs')

API

logs({pathToCode, verbose, destroy, production}, callback)

Takes a parameter object as first argument which accepts the following properties:

  • pathToCode: required the local path to architect Function code relative to the current working directory, i.e. src/http/get-index
  • verbose: verbose super chatty mode
  • destroy: if truthy will delete logs via logs.destroy, otherwise will read logs via logs.read
  • production: if truthy will target your arc project's production environment, otherwise will default to staging

By default will read logs from the staging environment. If the destroy property is truthy, logs instead will be destroyed.

logs.read({name, pathToCode, ts}, callback)

Will read logs from aws.CloudWatchLogs, invoking getLogEvents for log retrieval.

Takes a parameter object as first argument which accepts the following properties:

  • name: the CloudFormation StackName passed to listStackResources within which to search Function logs. Note that this is inferred from your application name, environment and specific function you are querying - tread carefully!
  • pathToCode: required the local path to architect Function code relative to the current working directory, i.e. src/http/get-index
  • ts: timestamp to use as a start time for displaying length of time details (i.e. Date.now())

callback will be invoked with an error if an error arises during execution. Otherwise, callback will be invoked without arguments.

logs.destroy({name, pathToCode, ts}, callback)

Will delete logs from aws.CloudWatchLogs, invoking deleteLogGroup.

Takes a parameter object as first argument which accepts the following properties:

  • name: the CloudFormation StackName passed to listStackResources within which to search Function logs. Note that this is inferred from your application name, environment and specific function you are querying - tread carefully!
  • pathToCode: required the local path to architect Function code relative to the current working directory, i.e. src/http/get-index
  • ts: timestamp to use as a start time for displaying length of time details (i.e. Date.now())

callback will be invoked with an error if an error arises during execution. Otherwise, callback will be invoked without arguments.