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

@opengis/fcore

v0.0.1-beta.12

Published

Reusable backend foundation for OpenGIS Node.js applications

Readme

@opengis/fcore

Reusable backend foundation for OpenGIS Node.js applications: config, typed application context, PostgreSQL, Redis, S3 file storage, audit, trusted Resource CRUD, Core modules, Fastify integration and SQL migration runner.

Install

npm install @opengis/fcore

Bootstrap

import { createFCore } from '@opengis/fcore';
import resources from './resources/index.js';

export const ctx = await createFCore({ resources });
import Fastify from 'fastify';
import fcoreFastify from '@opengis/fcore/fastify';
import { ctx } from './app.js';

const app = Fastify();
await app.register(fcoreFastify, { ctx });
await app.listen({ port: ctx.config.port });

Resource

All dynamic table/column identifiers come from registered ResourceContract metadata. Values are SQL parameters.

Migrations

Project SQL files stay in ./migrations. Build the package/application, then run fcore-migrate or import runMigrations().

Module service convention

Module services are plain async functions with the canonical service(params, ctx) signature. ctx is passed explicitly from fastify.ts to each module route.ts; there is no service.ts or createService() factory.

Structure

@opengis/fcore
├── src/
│   ├── plugins/
│   │   ├── logger/
│   │   ├── redis/
│   │   ├── pg/
│   │   ├── file/
│   │   ├── audit/
│   │   └── resource/
│   ├── modules/
│   │   ├── auth/
│   │   ├── access/
│   │   ├── resource/
│   │   ├── file/
│   │   ├── template/
│   │   └── system/
│   ├── migrations/
│   ├── config.ts 		# loadConfig
│   ├── context.ts		# createContext, set, get
│   ├── errors.ts		# standard Errors
│   ├── fastify.ts		# fastify Plugins  
│   ├── fcore.ts		# createFcore 
│   └── index.ts		# export type, methods, etc
├── test/	
├── engineering/
├── package.json
└── tsconfig.json