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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@cortec/server

v1.9.3

Published

<description>

Readme

@cortec/server

Module Overview

@cortec/server provides a simple HTTP server abstraction for Node.js, designed to integrate seamlessly with the Cortec context and configuration system. It allows you to start an HTTP server with a custom request handler or a named handler module, and supports configuration-driven port selection.

This module is typically used as the entry point for web services in a Cortec-based application.


Configuration Options

Where to put config: Place your server config in config/default.yml (or your environment-specific config file).

Schema:

server:
  http:
    port: 8080 # The port number the server will listen on (default: 8080)

Field-by-field explanation:

  • server: Root key for server config.
  • http: Section for HTTP server options.
    • port: The port number the server will listen on.
      • Type: number
      • Default: 8080
      • Required: No (defaults to 8080 if not set)

TypeScript interface:

interface IServerConfig {
  http: {
    port: number;
  };
}

How config is loaded: The config is loaded automatically by the @cortec/config module and validated at runtime. Access it in code via:

const config = ctx.provide<IConfig>('config');
const serverConfig = config?.get<IServerConfig>('server');

If config is missing, the server will default to port 8080. If invalid, an error is thrown at startup.


Example Usage

1. Using a Custom Request Handler

import CortecServer from '@cortec/server';
import http from 'node:http';

const handler: http.RequestListener = (req, res) => {
  res.writeHead(200, { 'Content-Type': 'text/plain' });
  res.end('Hello from Cortec Server!');
};

const serverModule = new CortecServer(handler);

// Add to Cortec context and load as usual
context.use(serverModule);
await context.load();

2. Using a Named Handler Module

Suppose you have a handler module registered in your context (e.g., via @cortec/polka):

const serverModule = new CortecServer('polka');
context.use(serverModule);
await context.load();

The server will look up the handler by name in the context.


Lifecycle

  • load(ctx, sig): Starts the HTTP server on the configured port.
  • dispose(): Gracefully shuts down the server.

Notes

  • The server will throw an error if the handler module is not found in the context.
  • The port can be configured via your config files; if not specified, it defaults to 8080.

See Also