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

@vilancer/filelinks-core

v1.0.3

Published

defineLinks config, staged matching, and Cursor AI agent helpers for the @vilancer/filelinks CLI (filelinks check --run-agents)

Readme

@vilancer/filelinks-core

Library for filelinks — the tool that declares file-to-file relationships, checks them against staged git changes, and can run Cursor AI agents to update linked files.

This package is what your app imports. The CLI binary is @vilancer/filelinks (filelinks on the PATH).

Why you need this package

filelinks.config.ts lives in your project and must resolve:

import { defineLinks } from '@vilancer/filelinks-core';

Install both:

pnpm add -D @vilancer/filelinks @vilancer/filelinks-core
# or: npm install --save-dev @vilancer/filelinks @vilancer/filelinks-core

What this library provides

  • defineLinks — typed config export (links + global options)
  • Config loadingloadFileLinksConfig (jiti loads .ts configs)
  • Staged matchingmatchStagedLinks / classifyStagedLinks (minimatch + linkType)
  • AI / Cursor agents — prompt assembly, provider registry, run policies, Cursor SDK integration used by filelinks check --run-agents

Config example (with AI agent)

import { defineLinks } from '@vilancer/filelinks-core';

export default defineLinks(
  [
    {
      trigger: 'apps/api/src/routes/user.ts',
      affects: [
        { file: 'apps/api/docs/openapi.yaml', reason: 'Keep OpenAPI in sync' },
      ],
      severity: 'warn',
      agent: {
        provider: 'cursor',
        runtime: 'local',
        model: 'composer-2.5',
        runPolicy: 'trigger-or-affects',
        local: { cwd: '.' },
      },
    },
  ],
  {
    agent: {
      provider: 'cursor',
      runtime: 'local',
      model: 'composer-2.5',
      local: { cwd: '.' },
    },
    prompt: { temperature: 0.2 },
  },
);

Then run the CLI from @vilancer/filelinks:

filelinks add                 # creates filelinks.config.ts if missing
filelinks check
filelinks check --run-agents  # Cursor AI updates for policy-eligible links

Related package

| Package | npm | Role | |---------|-----|------| | @vilancer/filelinks-core (this) | npm | Library API | | @vilancer/filelinks | npm | CLI: check, list, add, --run-agents |

Full docs: github.com/Vilancer/filelinks.