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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@codeinkit/http-trigger

v1.1.1

Published

A basic TypeScript project

Readme

HTTP Trigger

A simple HTTP server for handling API routes with support for URL parameters, CORS, and static file serving.

Features

  • URL Parameter Support: Routes can include dynamic parameters using :paramName syntax
  • CORS Support: Configurable CORS headers
  • Static File Serving: Serve static files from a specified directory
  • Query Parameters: Automatic parsing of query string parameters
  • JSON Body Parsing: Built-in JSON request body parsing
  • URL-encoded Body Parsing: Support for form data parsing

URL Parameters

You can define routes with dynamic parameters using the :paramName syntax:

// Example route file: users/[id].ts
export const triggers = [
  {
    type: 'http',
    method: 'GET',
    path: '/users/:id'
  }
];

export default async function(data: any, unsafe: any) {
  const { id } = data; // URL parameter is available in data
  return {
    status: 200,
    response: { userId: id, message: `User ${id} details` }
  };
}

Parameter Examples

  • /users/:id - matches /users/123, /users/abc, etc.
  • /posts/:postId/comments/:commentId - matches /posts/123/comments/456
  • /api/products/:category/:productId - matches /api/products/electronics/laptop

Usage

import HttpTrigger from './src/index';

const httpTrigger = new HttpTrigger(flows, unsafe, {
  origin: '*',
  methods: ['GET', 'POST', 'PUT', 'DELETE'],
  allowedHeaders: ['Content-Type', 'Authorization']
}, './public');

await httpTrigger.registerFolder('./routes');
httpTrigger.listen(3000);

Route Definition

Routes are defined in TypeScript files with the following structure:

export const triggers = [
  {
    type: 'http',
    method: 'GET', // HTTP method (GET, POST, PUT, DELETE, etc.)
    path: '/api/users/:id' // Route path with optional parameters
  }
];

export default async function(data: any, unsafe: any) {
  // data contains:
  // - URL parameters (e.g., { id: '123' })
  // - Query parameters (e.g., { page: '1', limit: '10' })
  // - Request body (if parsed)
  
  // unsafe contains:
  // - req: http.IncomingMessage
  // - res: http.ServerResponse
  // - headers: request headers
  
  return {
    status: 200,
    response: { message: 'Success' },
    headers: { 'Custom-Header': 'value' }, // optional
    redirect: '/new-location', // optional
    httpSent: false // set to true if you manually send response
  };
}

Body Parsing

Use the provided helper functions to parse request bodies:

import { handleJson, handleUrlEncodedExtended } from './src/index';

export default async function(data: any, unsafe: any) {
  // Parse JSON body
  const jsonData = await handleJson(data, unsafe);
  
  // Parse URL-encoded form data
  const formData = await handleUrlEncodedExtended(data, unsafe);
  
  return {
    status: 200,
    response: { received: jsonData.body }
  };
}