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

@paulio/p69-files

v1.0.0-rc-3

Published

Injects compile time tokens into CSS files

Readme

Made to be Plundered Latest version Release date

P69 Files

Adds CSS file and file watching support to P69.

  • P69: https://github.com/PaulioRandall/p69
  • P69 Files: https://github.com/PaulioRandall/p69-files
  • P69 Svelte: https://github.com/PaulioRandall/p69-svelte
  • P69 Util: https://github.com/PaulioRandall/p69-util

Contents

Example

Given my-styles.p69 some where under /src:

.my-class {
	color: $color.normal;
	font-weight: bold;

	font-size: $font.size.md;
	width: $width('lg');
}

.my-class:hover {
	color: &color.highlight;
}

And more-styles.p69 some where under /src:

.another-class {
	font-size: $font.size.sm;
	width: $width('ms');
}

Then executing p69-to-css.js:

import P69 from 'p69-files'

const mappings = {
	color: {
		normal: 'burlywood',
		highlight: 'crimson ',
	},
	font: {
		size: {
			sm: '0.8rem',
			md: '1rem',
			lg: '1.2rem',
		},
	},
	width: (size = 'md') => {
		const sizes = {
			xs: '5rem',
			sm: '10rem',
			md: '15rem',
			lg: '20rem',
			xl: '25rem',
		}

		return sizes[md]
	},
}

await P69.file(tokens)
/*
	await P69.files(mappings, {
		src: './src',
		dst: './src/app.css',
	})
*/

You can pass multiple mappings. It will search each mapping in order until it finds a value, e.g. P69.file([fonts, colors])

Produces src/app.css:

/* Note: order may vary */
.my-class {
	color: burlywood;
	font-size: 1rem;
	width: 20rem;
}

.my-class:hover {
	color: crimson;
}

.another-class {
	font-size: 0.8rem;
	width: 10rem;
}

^Back to contents

Options

P69(
	mappings,
	options: {
		// onError is called when an error occurs.
		//
		// If the error isn't thrown then processing will
		// continue for the remaining tokens.
		onError: (err, token) => {
			// By default, logs the error and carries on.
		},

		// Directory to scan for .p69 files.
		src: "./src",

		// Output file. Amalgamates all compiled .p69
		// CSS into one file.
		//
		// If set as undefined, null, or empty string,
		// each .p69 file will be written as a .css file
		// in the same folder. It will overwrite if
		// already exists.
		dst: "./src/app.css"
	}
)

^Back to contents

Watching

Unfortunatly, I've had little success in getting a JavaScript token file and its dependencies to reload on change. ECMAScript modules were designed to load once and once only.

import P69 from 'p69'

const mappings = {
	// ...
}

// Does not block.
// Currently uses chokidar.
const stopWatching = P69.watch(mappings)

// ...

await stopWatching()

Watch Options

P69.watch(
	mappings,
	options: {
		// onError is called when an error occurs.
		//
		// If the error isn't thrown then processing will
		// continue for the remaining tokens.
		onError: (err, token) => {
			// By default, logs the error and carries on.
		},

		// Directory to scan for .p69 files.
		src: "./src",

		// Output file. Amalgamates all compiled .p69
		// CSS into one file.
		//
		// If set as undefined, null, or empty string,
		// each .p69 file will be written as a .css file
		// in the same folder. It will overwrite if
		// already exists.
		dst: "./src/app.css",

		// Options to file watching package: Chokidar.
		//
		// These are the defaults. They extend Chokidar's (v4)
		// defaults, see https://github.com/paulmillr/chokidar.
		chokidar: {
			// Ignore everything except .p69 files.
			ignored: (path, stats) => stats?.isFile() && !path.endsWith('.p69'),

			// Otherwise recompile triggers for each dir under src during start up.
			ignoreInitial: true,

			// A little idiot proofing.
			followSymlinks: false,

			// I don't know what is suitable but seems to work fine.
			// Extend 'stabilityThreshold' if you experience file update issues.
			awaitWriteFinish: {
				stabilityThreshold: 999,
				pollInterval: 200,
			},

			// Avoid triggering recompile twice when some tool deletes and
			// writes a file, rather than updating it.
			atomic: 200,
		},
	}
)

^Back to contents