Some notes and tools for reverse engineering / deobfuscating / unminifying obfuscated web app code.
| # Workflow Orchestration | |
| ## 1. Plan Mode Default | |
| - Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions) | |
| - If something goes sideways, STOP and re-plan immediately — don’t keep pushing | |
| - Use plan mode for verification steps, not just building | |
| - Write detailed specs upfront to reduce ambiguity | |
| ## 2. Subagent Strategy | |
| - Use subagents liberally to keep main context window clean |
Rspack uses npm's optional dependencies feature combined with platform filtering to ensure users only download the binary for their specific OS and architecture.
The main @rspack/binding package (crates/node_binding/package.json) declares all platform-specific packages as optionalDependencies:
claude cosplaying as the V8-team speaking at JSConf
When ES6 Proxies shipped in 2015, they came with an asterisk. The spec gave us something genuinely powerful—metaprogramming primitives that could intercept fundamental object operations—but the performance story was grim. Internal benchmarks showed property access through a Proxy running 50-100x slower than direct access. We told developers "use sparingly" and hoped for the best.
A Chrome DevTools script to extract structured comment data from GitHub discussion threads.
- Navigate to a GitHub discussion page
- Open Chrome DevTools Console (
Cmd+Option+Jon Mac,Ctrl+Shift+Jon Windows) - Paste the extraction script
- Run it to get JSON structured data
A question on the OpenJS Foundation Slack made me wonder about this enough to go down the rabbit hole
npm config references a
init-modulewhich is a path to a JS file that is passed to init-package-json which in turn passes it to promzard which uses the raw Module pattern to load the contents of the file into node/v8
A list of select principles that have been particularly useful in helping design, refine, and debug complex systems (both computer & human)
Any organization that designs a system (defined broadly) will produce a design hose structure is a copy of the organization's communication structure.
| @exemplar/native-storybook: 7 | |
| @exemplar/storybook: 9 | |
| @exemplar/storybook-react: 35 | |
| @exemplar/storybook-react-native: 6 | |
| @gasket/assets: 310 | |
| @gasket/cli: 641 | |
| @gasket/data: 225 | |
| @gasket/engine: 505 | |
| @gasket/fetch: 212 | |
| @gasket/helper-intl: 230 |
| # Ignore things not in the gist | |
| * | |
| !facade.js | |
| !hebcal.js | |
| !README.md | |
| !temporal.js | |
| !why.png |
| const puppeteer = require('puppeteer'); | |
| const util = require('util'); | |
| const fs = require("fs"); | |
| const path = require('path'); | |
| (async (url) => { | |
| const browser = await puppeteer.launch(); | |
| const page = await browser.newPage(); | |
| await page.coverage.startCSSCoverage(); | |
| await page.goto(url); |