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

@stone-ton/lambda-json-rpc

v3.481.6

Published

Biblioteca AWS Lambda JSON-RPC para Server e Cliente em TypeScript

Downloads

101

Readme

Biblioteca AWS Lambda JSON-RPC para Server e Cliente em TypeScript

Visão Geral

Esta biblioteca oferece um framework simples e leve para construir um servidor e cliente utilizando funções AWS Lambda no padrão JSON-RPC (Remote Procedure Call). Com esta biblioteca, você pode facilmente criar aplicações serverless que utilizam AWS Lambda para lidar com chamadas de procedimentos remotos.

Exemplo

Servidor

import { Handler } from 'aws-lambda'
import { RPCHandler } from '@stone-ton/lambda-json-rpc'

type Methods = {
  test(params: { message: string }): string
}
type MethodTest = (
  params: Parameters<Methods['test']>[0],
  serverParams: JSONRPCMetadata
) => ReturnType<Methods['test']>

const method: MethodTest = (message) => {
  return 'Olá ' + message
}

const rpc = new RPCHandler<Methods>()

rpc.addMethod('test', method)


export const handler: Handler = async (event, context) => {
  return rpc.handler(event, context)
}

Cliente

import { RPCCLient } from 'aws-lambda'
import { LambdaClient } from '@aws-sdk/client-lambda'
type Methods = {
  test(params: { message: string }): string
}
const lambdaClient = new LambdaClient({})
const client = new RPCCLient<Methods>(lambdaClient)

const result = await client.request(
  'test',
  { message: 'foo' },
  {
    function_name: 'lambda-test',
    metadata: {
      request_id: '12',
      service: 'ton/monorepo',
      author: {
        id: '1234',
      },
    },
  },
)

Opentelemetry

Antes de começar a usar a biblioteca, certifique-se de definir as variáveis de ambiente necessárias:

  • OTLP: Deve ser definido como true para habilitar o rastreamento com OpenTelemetry.
  • OTLP_TIMEOUT: Define o limite máximo de espera em milissegundos para o envio do trace pela lambda, com o valor padrão de 200ms caso não seja definido.
  • OTLP_TRACE_URL: Deve ser definido com a URL do servidor OpenTelemetry Collector, por exemplo, localhost:4318.
  • OTLP_LAMBDA_DEBUG: Quando definido como true, acrescenta detalhes de requisição e resposta da lambda json rpc. Atenção à possível presença de dados sensíveis.