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

@nestling/context

v1.8.1

Published

Context Module for NestJS

Downloads

428

Readme

Context module for NestJS

Conventional context module.

Use it to store context about the application.

Setup

Global Context

import { ContextModule } from '@nestling/context'

@Module({
  imports: [
    ContextModule
  ]
})
export class ApplicationModule {}

@Component()
export class MyMiddleware {
  constructor(
    private context: ContextService
  ) {}
  
  someMethod() {
    this.context.set('someGlobalContext', ...)
  }
}

@Component()
export class MyService {
  constructor(
    private context: ContextService
  ) {}
  
  someMethod() {
    if (this.context.has('someGlobalContext')) {
      this.context.get('someGlobalContext')
      ...
    }
  }
}

Per Request / Response Context

First make sure the ContextModule is imported, it will automatically define a ContextModel on each request / response pair, this is done internally by the ContextInterceptor.

The context is shared among request & response, representing the same context instance.

imports: [
  ContextModule 
]

Functions

The context can be retrieved from either the request or the response.

 request.context.set('prop', value')
 request.context.get('prop'')
 request.context.has('prop'')
 
 response.context.set('prop', value')
 response.context.get('prop'')
 response.context.has('prop'')

Convenience functions are also available:

import {
  hasContext,
  getContext,
  setContext
} from '@nestling/context'

// sets .context on request
setContext('jwt', decoded, request)

// additional functions:
hasContext('jwt', request)
getContext<ExpectedType>('jwt', request) // ExpectedType or null

@Context decorator

The @Context decorator can be used to retrieve context which was previously set on the request.

If @Context() is called with no arguments it will supply the whole context.

@Controller()
export class MyController {
  @Get()
  async getPosts(
    @Context('jwt') jwt,
    @Context('nested.path') nestedPath,
    @Context(['nested', 'path', 'also']) nestedPathAlso
    @Context() context
  ) {}
}

Example Context Supplier

Note that although the context is set on the request, it will also be available on the response.

import {
  CanActivate,
  Injectable,
  ExecutionContext
} from '@nestjs/common'
import { ErrorMessage } from '@nestling/errors'
import * as jwt from 'jsonwebtoken'
import { ConfigService } from '@nestling/config'
import { setContext } from '@nestling/context'

import { JWTConfig } from './types'

@Injectable()
class JsonWebtokenGuard implements CanActivate {
  constructor (
    private config: ConfigService
  ) {}

  async canActivate (executionContext: ExecutionContext): Promise<boolean> {
    const {
      jwt: {
        contextKey = 'jwt',
        secret,
        header = 'authorization'
      }
    }: JWTConfig = this.config as any

    const httpContext = executionContext.switchToHttp()
    const request = httpContext.getRequest()
    const { headers } = request

    if (typeof headers[header] === 'string') {
      const parts = headers[header].split(' ')

      if (parts[0] === 'Bearer') {
        const token = parts[1]
        const decoded: any = jwt.verify(token, secret)

        setContext(contextKey, decoded, request)

        return true
      }
    }

    throw new ErrorMessage('auth:unauthorized')
  }
}