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

@latta/nestjs

v1.0.1

Published

![Latta logo](../../docs/logo.svg)

Downloads

12

Readme

@latta/nestjs

Latta logo

npm version

Seamlessly integrate exception monitoring into your NestJS applications with Latta

Overview

The @latta/nestjs library provides robust error tracking and monitoring for your NestJS applications. It automatically captures and reports both process-level exceptions and request-specific errors to the Latta reporting system using NestJS interceptors.

Features

  • 🔄 Automatic exception handling via interceptors
  • 🚀 Quick & easy setup
  • 🛠️ Customizable options
  • 📊 Comprehensive error reporting
  • 📝 Detailed request and response logging

Installation

Install the package using npm:

npm install @latta/nestjs

Or using yarn:

yarn add @latta/nestjs

Quick Start

Adding Latta to your NestJS application requires just one line of code in your bootstrap function:

import { NestFactory } from '@nestjs/core';
import { LattaInterceptor } from '@latta/nestjs';
import { AppModule } from './app.module';

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  
  // Add Latta interceptor
  app.useGlobalInterceptors(new LattaInterceptor(process.env.LATTA_API_KEY));
  
  await app.listen(3000);
}
bootstrap();

Configuration

Interceptor Initialization

The Latta interceptor can be configured with options:

import { LattaInterceptor } from '@latta/nestjs';

const interceptor = new LattaInterceptor(
  process.env.LATTA_API_KEY,
  {
    verbose: true // Enable detailed logging
  }
);

app.useGlobalInterceptors(interceptor);

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | verbose | boolean | false | When enabled, Latta will log detailed information to the console |

interface LattaInterceptorOptions {
  verbose?: boolean;  // Enable/disable detailed logging
}

Examples

Controller-Level Implementation

import { Controller, Get, UseInterceptors } from '@nestjs/common';
import { LattaInterceptor } from '@latta/nestjs';

@Controller('api')
@UseInterceptors(new LattaInterceptor(process.env.LATTA_API_KEY))
export class ApiController {
  @Get('data')
  getData() {
    // Your route logic here
  }
}

Error Handling

Latta automatically captures errors thrown in your controllers:

@Controller('api')
export class ApiController {
  @Get('resource')
  getResource() {
    throw new Error('This error will be captured by Latta');
  }
}

Best Practices

  1. Use environment variables for your API key
  2. Add the Latta interceptor in your application bootstrap
  3. Enable verbose logging during development

Debugging

For debugging purposes, you can enable verbose logging:

const interceptor = new LattaInterceptor(process.env.LATTA_API_KEY, { verbose: true });

This will output detailed information about Latta's operation to the console.

Support

If you encounter any issues or need assistance:

License

This project is licensed under the MIT License - see the LICENSE file for details.