Results for wtf-code

understand code the honest way.

A well-tested WTF-8 encoder/decoder written in JavaScript.

chdir in chainer fashion + read file

Encode and decode [WTF-8](https://simonsapin.github.io/wtf-8/) with a similar API to [TextEncoder](https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder) and [TextDecoder](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder).

A replacement for process.exit that ensures stdio are fully drained before exiting.

Querystringify - Small, simple but powerful query string parser.

Convert between keyboard keycodes and keynames and vice versa.

markdown plugin for wtf_wikipedia

text-summary plugin for wtf_wikipedia

node ``` { "extends": "wtf-devconfigs/tsconfigs/node/tsconfig.json", "include": ["eslint.config.mjs", "src/**/*", "test/**/*"], "compilerOptions": { "noEmit": true } } ```

Get all children of a pid

Utility to help find out why Node isn't exiting

A JavaScript ANSI color/style management. ANSI parsing. ANSI to CSS. Small, clean, no dependencies.

Find out what the function you need

One-command launcher for the x402.wtf CLAWD terminal, APIs, and Solana Clawd TUI.

wikimedia api plugin for wtf_wikipedia

html plugin for wtf_wikipedia

Type checker for JS

AI-powered academic writing commands for Claude Code, Gemini CLI, and OpenCode. Papers, proposals, presentations, and posters — structured, cited, verified.

Check whether a binary exists in the PATH environment variable

[](https://github.com/null/wtf-vue/issues) [](https://www.npmjs.com/package/wtf-vue)

Winston-lite-esque Log lib for terminal and browser debugging, with piles of unignorable log tags and marker styles.

Where's The File? Blazing-fast interactive terminal file finder and CLI searcher.

A drop-in replacement for `redux-thunk` that allows middleware to detect that a thunk has been dispatched from within another thunk

I sometimes get a little descriptive with my variable names, so when you're doing a lot of work specifically with one object, it gets especially ugly and repetetive, making the code harder to read than it needs to be: @contract_participants_on_drugs.contract_id = params[:contract_id] @contract_participants_on_drugs.participant_name = params[:participant_name] @contract_participants_on_drugs.drug_conviction = DrugConvictions.find(:wtf => 'this is getting ridiculous') ... And so on. It gets ridiculous. Utility Belt implements a with(object) method via a change to Object: class Object #utility belt implementation def with(object, &block) object.instance_eval &block end end Unfortunately, that just executes the block in the context of the object, so there isn't any crossover, nor can you perform assignments with attr_accessors (that I was able to do, anyway). So, here's With.object() to fill the void. With.object(@foo) do a = "wtf" b = "this is not as bad" end In the above example, @foo.a and @foo.b are the variables getting set. If you prefer, you can require 'with_on_object' instead and use the notation with(object) do ... end. The tests in the /test directory offer more examples of what's been implemented and tested so far (except where noted - namely performing assignment to a variable that was declared outside the block, and is not on @foo). Not everything is working yet, but it works for the simplest, most common cases I've run up against. More complex tests are on the way, along with code to make them pass. Special thanks to Reg Braithwaite, for help and ideas along the way.