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

matte-engine

v0.1.5

Published

Package that compiles AsciiMath-HTML to complete, searchable websites. (with SVG-graphics)

Downloads

3

Readme

matte-engine

Package that compiles AsciiMath-HTML to complete, searchable websites. (with SVG-graphics)

Disclaimer: This package ain't your all purpose, general package. This is niched against a fixed folder structure and fixed document structures. Be aware, and look at the examples for success.


This package exposes a function and a CLI.

module usage

npm i matte-engine

async function main(){
    var compile = require('matte-engine').compile
    await compile('matte/flervariabelanalys')
    console.log('Profit')
}
main()

CLI

npm i -g matte-engine

matte-engine init matte/flervariabelanalys
# Created empty boilerplate in matte/flervariabelanalys
matte-engine matte/flervariabelanalys

Conventions

Note: You don't really have to care about the folder structure if you're using the CLI to init your projects, and then dumping the root-folder at a web server. Just sayin

Uncompiled file structure:

project/
├── src
│   ├── boilerplate.html
│   ├── fl1.html
└── style.css

Note the convention of namespacing the files src/fl*.html. The boilerplate is there for practical reasons only, in case you need to take notes quickly (ie cp boilerplate.html fl4.html && vim fl4.html).

Compiled file structure:

project/
├── data.js
├── fl1.html
├── index.html
├── src
│   ├── boilerplate.html
│   ├── fl1.html
└── style.css

The package should create these files after compilation: data.js: File containing search information about files fl*.html: src/fl*.html but with pre-rendered SVG graphics instead of AsciiMath index.html: Index for site

fl*.html

<!DOCTYPE html>
<html>
<head>
    <script src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=AM_HTMLorMML"></script>
    <link rel="stylesheet" href="../style.css">
</head>
<body>
    <div>
        Your stuff here `x = 0`
    </div>
    <div>
        These divs are seperated by a tiny amount, making readable "pages"
    </div>
</body>

This setup ensures that you are able to use live-server to live preview your changes to this file.