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

fmprops

v1.0.4

Published

Parses webviewer props from FileMaker

Readme

fmprops

Parses webviewer props from FileMaker.

Installation

npm install fmprops

Setup

Add a <meta> tag in your HTML with the dev-url attribute pointing to your local development server:

<meta dev-url="http://localhost:5173" />

In development mode (when the page URL matches dev-url), props are read from the props query parameter:

http://localhost:5173?props={"name":"John","age":30}

In production mode (inside a FileMaker WebViewer), the ##PROPSPLACEHOLDER## string in the source is replaced by FileMaker with the actual props object before the page is rendered.

Usage

JavaScript

import { loadFmProps, getFmProps } from 'fmprops';

// Load and parse props (call once on startup)
const props = loadFmProps();

// Retrieve the loaded props later from anywhere
const props = getFmProps();

TypeScript

import { loadFmProps, getFmProps } from 'fmprops';

// Load and parse props (call once on startup)
const props = loadFmProps();

// Retrieve the loaded props later from anywhere
const props = getFmProps();

The package includes built-in type declarations so no additional @types package is needed.

API

loadFmProps()

Loads and parses the props from FileMaker. Stores them globally and returns the parsed props object.

  • In development: reads from the props URL query parameter
  • In production: uses the value injected by FileMaker into the ##PROPSPLACEHOLDER## string

Returns: Record<string, any> - the parsed props object.

getFmProps()

Returns the props that were previously loaded by loadFmProps().

Returns: Record<string, any> - the loaded props object.

License

MIT