phryneas

Inspired by https://spwoodcock.dev/blog/2026-02-04-potensic-atom-redux/

This is 100% written by Codex and not checked for any sanity. It looks like it might do the job for me but use at your own risk!

Resources:

• https://spwoodcock.dev/blog/2026-02-04-potensic-atom-redux/

Potensic JSON -> Litchi CSV

Convert a Potensic-style waypoint JSON file (array of waypoint objects) to a Litchi-importable CSV:

phryneas

// Higher Kinded base type
// inspired by 
// https://github.com/arktypeio/arktype/blob/main/ark/util/hkt.ts
// and
// https://github.com/gvergnaud/hotscript/blob/main/src/internals/core/Core.ts

declare const rawArgs: unique symbol;
type rawArgs = typeof rawArgs;

interface Hkt {

phryneas

{
  "replay": { 
     "url": "https://static.replay.io/downloads/linux-gecko-20220331-59d0a686993f-ffd8d6280276.tar.bz2",
     "sha256": "0pf1ihxkx8dr1hn8v84sb8pgyg4xwpvjlk6jlp5bkpzp5zhyskqy"
  },
  "recordreplay-lib": { 
     "url": "https://static.replay.io/downloads/linux-recordreplay-ffd8d6280276.tgz",
     "sha256": "1sif40b7zk5mxibqpncdv00yxp7kh6jl37jq12ggm36nswwr9l7g"
  }
}

phryneas

/**
  This brute forces all possible () combinations by interpreting the binary 
  representation of an increasing number with 0 as ( and 1 as ).
  Works fine for n<15. For bigger n, the amount of results will be too big for memory.
*/
function fromParens(n) {
  let ret = [],
    targetLen = n * 2, // target string length
    max = Math.pow(2, targetLen), // maximum number to look at
    current, // current number

phryneas

node_modules

phryneas

{
  "name": "foofoo",
  "version": "1.0.0",
  "main": "index.js",
  "author": "Lenz Weber",
  "license": "MIT",
  "dependencies": {
    "@types/node": "^14.14.41",
    "typescript": "^4.2.4"
  }

phryneas

Do not create union types with Redux Action Types. It's most likely an antipattern.

So, there is a long-standing TypeScript & Redux pattern of creating a union RootAction type that contains all your application's action types. Sometimes, you would also create a lot of reducer-specific sub-unions. I think that this has always been a crutch - and given the options we have today, it's most likely an antipattern. So let's look at why it was used, where it was used and what you can use instead.

Why was it used? A look at typed Reducers.

Classically, these action union types were created to use the Discriminating Union pattern.

phryneas

Home

API Reference

Packages

Package	Description

phryneas

#!/usr/bin/env bash

#remove all git tags
git tag | xargs git tag -d

#re-apply all git tags with commit name => tag name
git log --pretty=%s---%H | sed -re 's/[^a-zA-Z0-9-]/_/g;s/---/ /' | xargs -n2 git tag 

git tag --format="%(objectname) => %(refname)"

phryneas

/// <reference types="react" />
import { ComponentClass } from 'react';
import * as CSS from 'csstype';
import * as PropTypes from 'prop-types';
import React from 'react';

declare interface AbstractAction {
    type: string;
    meta: {
        counter: number;