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

@smartfront/server

v0.2.2

Published

Smartfront server operations SDK

Readme

@smartfront/server

Completed, validated router decisions bypass the extraction LLM. Unresolved parameters go through model interpretation first so supplied text, numbers and references can be extracted automatically. A confidently identified single operation produces pending.form only when interpretation still needs user input. Explicit custom-router form selections also bypass interpretation. Direct execution and form responses are marked local; model-extracted actions retain result follow-ups. Typed parameter form behavior.

Separate Jev/LLM routing and deterministic operation validation for Node and Fetch runtimes. Provider secrets stay server-side. The backend proposes operations; browser handlers execute them.

Set autoParameterForms: false in server options to collect unresolved parameters through model follow-up questions for all clients. Clients can also disable forms per configuration with the same flag. Either value of false takes precedence over explicit router form selections; fully resolved direct execution remains available. The default is true.

import { createFetchHandler } from '@smartfront/server';
export const POST = createFetchHandler({ apiKey: process.env.OPENROUTER_API_KEY!, allowNoGuard: false });
import { createNodeHandler } from '@smartfront/server';
app.post('/v1/chat', createNodeHandler({ apiKey: process.env.OPENROUTER_API_KEY! }, {
  authenticate: (request) => verifySession(request.headers.get('authorization')),
  rateLimit: (identity) => quotaStore.allow(identity!.tenantId, identity!.userId),
}));

verifySession must return verified { tenantId, userId } or reject. A publishable key is public project identification, not authentication. resolveServer(identity) supports tenant-owned credentials/configuration on each request. Requests use protocol version 1, byte limits and abort signals; errors use { error: { code, message } }. Keep debug off in production because diagnostic responses include context/prompts. Never trust browser schemas as server-side permissions.

The repository includes a standalone Docker/Node deployment under apps/server. Workspace build/test: npm run build -w @smartfront/server, npm run test -w @smartfront/server after building core.