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

@flect/transform

v3.0.0

Published

Data transformers for flect

Downloads

20

Readme

Introduction

Flect/transform is a library for building transformers between flect types.

Usage

// Given a type with references to another type,
// create a keyed version that looks like an FK in a DB. Then transform
// from that DB version to the real thing.

// First, the type we will refer/foreign-key to
const Engine = record({
	cylinderCount: numberType,
	arrangement: union(literal("L"), literal("V"), literal("W")),
	id: stringType
});
type Engine = Reify<typeof Engine>;

// Next the two versions of the referring type: one flat like a database,
// one with a direct reference.
// A mapped conditional would be neat here, but flect currently
// can't handle that :( Instead, we create a function for producing the
// two types.
const makeCarType = <E>(engineType: Type<E>) =>
	record({
		make: stringType,
		model: stringType,
		engine: engineType
	});
// Our two car types, each with their own way of specifying an engine
const DBCar = makeCarType(stringType); // By key
const Car = makeCarType(Engine); // By reference
type DBCar = Reify<typeof DBCar>;

// Create a little in-memory mock of a database table (or service, etc.)
// with engine data.
const indexEngine = (e: Engine) => [e.id, e] as const;
const engineDb = new Map(
	[
		{cylinderCount: 4, arrangement: "L" as const, id: "straight-4"},
		{cylinderCount: 6, arrangement: "V" as const, id: "V6"},
		{cylinderCount: 16, arrangement: "W" as const, id: "W16"}
	].map(indexEngine)
);

// Create a transformer that handles identity,
// records, and engineDb looksup. We assume
// lookups never fail, for simplicity.
const c = new ChainTransformer();
c.add(new IdentityTransformer());
c.addLoopRepo(RecordTransformer);
c.add(
	getSingletonTransformerRepository(
		stringType,
		Engine,
		(id) => engineDb.get(id)!
	)
);
// Get the transformer
const t = c.get(DBCar, Car);
expect(t).toBeDefined();

// Create a flat car record
const carRecord: DBCar = {
	make: "Honda",
	model: "Pilot",
	engine: "V6"
};
// Transform it
const car = t!(carRecord);
console.log(JSON.stringify(car));
/*
		Output:
			{
				"make": "Honda",
				"model": "Pilot",
				"engine": {"cylinderCount": 6, "arrangement": "V", "id": "V6"}
			}
	*/