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

@monitio/xfm

v1.0.0-release.custom.multiplatform

Published

Expandable Functional Markup

Readme

XFM

Expandable Functional Markup

  • Both expandable and already expanded.

Currently in development. Please do not use yet as it may cause issues with certain things not working as expected or not there at all.

See the Todo list for a list of things that have been implemented for each compiler logic.


A lot of the logic bit of the compiler logic is taken from Build a programming language from scratch by Tylerlaceby and modified. This is because I have never programmed a compiler or anything like this before and thought it would be an interesting concept to learn more.

I do not claim to have written all of the code. Some bits may be the exact same as his. He is also listed in the Credits.


Coded in TypeScript using Deno.

Credits | Todo list | Documentation for the formats | Examples / Syntax-guide


Idea:

XFM tries to bridge the gap between:

  • Existing programming langauges (like JavaScript, Typescript, C and Python)
  • Making websites simpler to make (without html so things like coding the website in the backend at the same time as coding the backend)
  • Styling (like tailwindcss and markdown)

How it works:

XFM uses multiple different file-types for different things (like JavaScript does with ESModules and CommonJS being seperate). These file-types are:

  • Style (.xfms - Compiles to CSS, Markdown or HTML and the user can choose which one to compile to)
  • Logic (.xfml - Compiles to JavaScript)
  • Website (.xfmw - Compiles to HTML with a mix of CSS and JS as well)

Each different file-type has:

  • The same compiler and CLI tool called XFMC.
  • A similar but different syntax that should be decently easy to use for experienced people.
  • Compatibility between different file-types so people can use one type in a different type.
  • Semi-compatibility with existing programming languages: Python, JS ESModules, TS and CSS.
  • Ability to be used on their own with external things like XFM - style compiled to CSS with HTML or XFM - logic to runnable JS code using NodeJS or Deno to run it.

The inner-workings of the compiler is basically 3 compilers mixed together for use together in a single executable or package (coming soon; for NPM, PNPM, Yarn). They all have their own seperate logic and work seperately but can call each other using the main code bit or CLI.

[!NOTE] No file-types have been implemented yet. Please wait until further commits for any use at all.

Documentation:

Because of the different file-types for different things, you will need a specific file-type for the specific documentation you want to read.

[!NOTE] Not all documentation has been written yet. At the moment (25th of April 2025), only progress on logic has been made.

Syntax examples:

[!NOTE] Not all syntax examples have been written yet. At the moment (25th of April 2025), only progress on logic has been made.