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

@typesugar/named-args

v0.1.0

Published

Named function arguments with compile-time validation — Kotlin-style kwargs for TypeScript

Readme

@typesugar/named-args

Named and reorderable function arguments for TypeScript, inspired by Kotlin, Swift, and Boost.Parameter.

The Problem

Positional arguments get unreadable fast:

createUser("Alice", 30, true, "admin", null, "UTC", false);
//         ^^^^^  ^^  ^^^^  ^^^^^^^  ^^^^  ^^^^^  ^^^^^
//         what do any of these mean?

The Solution

Wrap your function with namedArgs() and call it with an object — parameters are reordered to match the original positional signature automatically:

import { namedArgs, type ParamMeta } from "@typesugar/named-args";

function createUser(name: string, age: number, active: boolean) {
  return { name, age, active };
}

const params: ParamMeta[] = [
  { name: "name",   type: "string",  required: true,  position: 0 },
  { name: "age",    type: "number",  required: true,  position: 1 },
  { name: "active", type: "boolean", required: true,  position: 2 },
];

const create = namedArgs(createUser, params);

// Named call — order doesn't matter
create.namedCall({ active: true, name: "Alice", age: 30 });

// Positional still works
create("Alice", 30, true);

Default Values

Mark parameters as optional and provide defaults:

const params: ParamMeta[] = [
  { name: "name",     type: "string", required: true,  position: 0 },
  { name: "greeting", type: "string", required: false, defaultValue: "Hello", position: 1 },
];

const greet = namedArgs(greetFn, params);
greet.namedCall({ name: "World" });           // "Hello, World!"
greet.namedCall({ name: "World", greeting: "Hi" }); // "Hi, World!"

Builder Pattern

For functions with many parameters, the builder pattern reads better:

import { createBuilder } from "@typesugar/named-args";

const user = createBuilder(createUser, params)
  .set("email", "[email protected]")
  .set("name", "Alice")
  .set("age", 30)
  .build();

Builders are immutable — each .set() returns a new builder. You can branch from a partial builder:

const base = createBuilder(createUser, params)
  .set("name", "Alice")
  .set("age", 30);

const work = base.set("email", "[email protected]").build();
const personal = base.set("email", "[email protected]").build();

Error Handling

NamedArgsError is thrown for:

  • Missing required paramsreason: "missing_required"
  • Unknown paramsreason: "unknown_param"
import { NamedArgsError } from "@typesugar/named-args";

try {
  wrapped.namedCall({ name: "Alice" }); // missing "age"
} catch (err) {
  if (err instanceof NamedArgsError) {
    console.log(err.reason);       // "missing_required"
    console.log(err.paramName);    // "age"
    console.log(err.functionName); // "createUser"
  }
}

Phase 2: Compile-Time Rewriting

Phase 1 (current) resolves named args at runtime via a thin wrapper.

Phase 2 will use the @namedArgs macro to rewrite call sites at compile time, turning:

create.namedCall({ active: true, name: "Alice", age: 30 });

into:

createUser("Alice", 30, true);

Zero overhead — the object literal never exists at runtime.