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 🙏

© 2024 – Pkg Stats / Ryan Hefner

fulcrum-schema

v3.0.1

Published

Table schemas for Fulcrum apps

Downloads

6

Readme

Fulcrum Query Table Schema Build Status

Setup

npm install -g browserify

Build

make

Distribute

Builds the final output. The main output file dist/fulcrum-schema.js.

make

Deploying

When making changes to this library, the fulcrum-schema.js file needs to be copied to the Fulcrum web app directory in public. At the same time the fulcrum-query repo needs to be upgraded to use the new version.

DO NOT change the template.sql in the web app without a complete understanding of the side effects. In most cases a core schema change will have to be hand-coded and applied to all existing databases. The template.sql file represents the one-time V1 version of the query schema and should never change unless there's a very good reason.

Copy files to other repositories

Copies the build output and docs to the other repositories (each are optional, but at least one is needed).

You can define the paths to the Fulcrum repos using environment variables in your shell config:

export FULCRUM_ANDROID=/path/to/android/app
export FULCRUM_IOS=/path/to/ios/app
export FULCRUM_WEB=/path/to/web/app
export FULCRUM_SITE=/path/to/website

Or you can assign them in the make command:

FULCRUM_SITE=$HOME/dev/fulcrumapp.com make dist copy

Once you have the environment variables set, you can run:

make copy

or

make dist copy # clean, build and deploy everything

Tests

make test