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

@redhare/context

v0.0.2

Published

In NestJS we need a context which can be created for every request. This context can contains some information we need for any place can be access.

Downloads

2

Readme

@infra-node-kit/context

In NestJS we need a context which can be created for every request. This context can contains some information we need for any place can be access.

Since AsyncLocalStorage is used internally, the required Node.js version is >=14.15.2 that includes significant fixes.

Installation

yarn add '@infra-node-kit/context'

Basic Usage

first you need use the infraContextMiddleware first, in middleware will create context and add requestId on context.

import { infraContextMiddleware } from '@infra-node-kit/context';

const app = await NestFactory(AppModule);
...
app.use(infraContextMiddleware());

await app.listen(3000);

In you controller, service or any other place can import InfraRequestContext to get the context.

import { InfraRequestContext } from '@infra-node-kit/context'
@Controller('')
export class MyController {
  @Get()
  test(): string {
    const ctx: InfraRequestContext = InfraRequestContext.get()
    return ctx.requestId
  }
}

API

infraContextMiddleware(options)

  • options.requestIdKey default value is x-request-id, it define the key name of the response header which contain requestId.
  • options.upstreamRequestIdKey default value is x-request-id, it define the key name of the request header which contain requestId, if request has this header, the project will reuse this value.

InfraRequestContext.get()

  • this method can get the context object which the type is InfraRequestContext

infraRequestContext

infraRequestContext = InfraRequestContext.get()

  • infraRequestContext.requestId is a uuid for every request which first get from request[options.requestIdKey], if not exist, will generate a new UUID. This id will also add into http response headers, header key name is decide by options.requestIdKey

  • infraRequestContext.userInfo reserved for google login save userInfo

  • infraRequestContext.userInfoEncrypt reserved for google login save userInfo

  • infraRequestContext.extra reserved for user can save anything you need