Registry / web-framework / veryfront

veryfront

JSON →
library0.1.217jsnpmunverified

Veryfront is a full-stack framework designed for building AI-powered applications and agents using TypeScript and React. Currently in version 0.1.217, it exhibits a rapid release cadence with frequent patch updates, suggesting active and agile development, but also a rapidly evolving API. Key differentiators include its purpose-built architecture for autonomous agents with model routing, tool calling, and multi-agent composition. It integrates a complete React rendering stack (SSR, RSC) with file-based routing, server-side data fetching, API routes, middleware, and OAuth. The framework supports multiple JavaScript runtimes including Node.js, Deno, and Bun, and offers a dedicated platform for deployment, streamlining the development-to-production workflow for agentic applications.

npm install veryfront
INSTALL
IMPORT
SIG · VERYFRONT
V
veryfront
web-frameworkjavascriptv0.1.217
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

Agent
import { Agent } from 'veryfront';
const Agent = require('veryfront');
Veryfront is a modern, TypeScript-first framework. Use ES Modules for imports. The `Agent` symbol is central to defining AI agent logic.
Tool
import { Tool } from 'veryfront';
import Tool from 'veryfront';
Tools are typically named exports, used for defining Zod-validated functions that agents can call. This is part of the core AI functionality.
definePage
import { definePage } from 'veryfront/router';
import { definePage } from 'veryfront';
For file-based routing, page definitions (and similar routing utilities like `useRouter`, `Link`) are typically imported from a dedicated `veryfront/router` sub-path.

This code defines a simple AI Agent and a web search Tool using Veryfront's core APIs, demonstrating how agents can use tools to fulfill prompts.

import { Agent, Tool } from 'veryfront'; import { z } from 'zod'; // Define a tool that an agent can use const searchTool = new Tool({ name: 'web_search', description: 'Searches the web for a given query.', parameters: z.object({ query: z.string().describe('The search query'), }), handler: async ({ query }) => { // In a real application, this would call a search API console.log(`Executing web search for: ${query}`); return `Results for '${query}': Found information about Veryfront being a full-stack AI framework.`; }, }); // Define an agent that uses the tool const assistantAgent = new Agent({ name: 'Assistant', description: 'A helpful AI assistant that can answer questions and perform tasks.', systemPrompt: 'You are an AI assistant. You can use the provided tools to answer questions. If a question requires external knowledge, use the web_search tool. Provide concise and helpful answers.', tools: [searchTool], handler: async ({ prompt, runTool }) => { if (prompt.includes('Veryfront')) { const result = await runTool(searchTool, { query: 'What is Veryfront?' }); return `Based on my search: ${result}`; } return "I'm not sure how to answer that without searching."; }, }); console.log('Veryfront Agent and Tool defined. Run this with `veryfront dev` in your project.'); // To run this, you'd typically have a `pages` or `api` file that uses `assistantAgent` // For example, in `api/chat.ts`: // export default defineApiRoute({ // post: async ({ body }) => { // const response = await assistantAgent.handler({ prompt: body.message }); // return { status: 200, body: { reply: response } }; // }, // });
veryfront --version
Debug
Known issues
breakingAs a framework in the early `0.1.x` version range, Veryfront is likely to introduce frequent breaking changes to its API and conventions without major version increments. Developers should expect rapid evolution and consult release notes closely.
fix
Regularly review the official Veryfront documentation and GitHub release notes for specific migration guides. Pin exact package versions in `package.json` to prevent unexpected updates.
affects: >=0.1.0
gotchaThe `better-sqlite3` peer dependency is a native Node.js module. Installation can fail on environments missing required build tools (e.g., Python, C++ compilers) or when deploying to different architectures.
fix
Ensure your development and deployment environments have the necessary build tools (e.g., `build-essential` on Linux, Xcode command-line tools on macOS, Visual C++ Build Tools on Windows). Consider using Docker for consistent environments or verify pre-built binaries are available for your target platform.
affects: >=0.1.0
gotchaVeryfront leverages file-based routing for pages, API routes, and potentially other AI primitives like agents and tools. Misplacing files or incorrect naming conventions can lead to routes not being discovered or invoked.
fix
Adhere strictly to Veryfront's specified file system conventions (e.g., `pages/`, `api/`, `agents/`, `tools/`). Consult the 'Project Structure' and 'Pages & Routing' documentation for exact naming patterns and directory structures.
affects: >=0.1.0
gotchaLLM (Large Language Model) API keys and environment variables for AI providers (e.g., OpenAI, Anthropic) must be correctly configured for agents to function. Failure to do so will result in runtime errors when attempting to use AI capabilities.
fix
Ensure all required environment variables for your chosen LLM providers (e.g., `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`) are set correctly in your development environment (`.env` file) and deployment environment. Verify their accessibility in server-side contexts.
affects: >=0.1.0
Errors
Common errors & fixes
Error: The module 'better-sqlite3.node' was compiled against a different Node.js version
Native module `better-sqlite3` was installed for a different Node.js version than the one currently in use, or build tools were missing during installation.
fix
Delete `node_modules` and `package-lock.json` (or `yarn.lock`, `pnpm-lock.yaml`). Ensure correct Node.js version is active (`nvm use <version>`), then reinstall: `npm install` (or `yarn`, `pnpm install`).
TypeError: Cannot read properties of undefined (reading 'handler') at Agent.runTool
An AI Agent tried to call a `Tool` that was either not correctly defined, not passed in the `tools` array during agent initialization, or its `handler` property is missing/undefined.
fix
Verify the `Tool` instance is correctly constructed with a `handler` function and is included in the `tools` array when instantiating the `Agent`. Check for typos in tool names when calling `runTool`.
404 Not Found - Page or API route not found for path: /my-agent-endpoint
Veryfront's file-based routing system did not find a corresponding file for the requested URL, indicating an incorrect file path, name, or missing export for a page or API route.
fix
Review your project structure and the `pages/` or `api/` directories. Ensure the file name (e.g., `my-agent-endpoint.ts` for `/api/my-agent-endpoint`) and its exported components/handlers (`export default function handler...`) match the expected routing conventions.
Upgrade
Version history
0.1.217latest on npm
Audit
Dependencies
better-sqlite3requiredPeer dependency required for local data storage and potentially other internal features, which is a common pattern for full-stack frameworks needing persistent local state. It's a native module.
Agent activity
36 hits · last 30 days
node
30
OpenAI (training)
1
Resources
veryfront — npm install veryfront · libregistry