⚡ ESLINT-BACK-TO-THE-FP --- TIME CIRCUITS EDITION ⚡

"When this lint config hits 88 miles per hour... your bugs disappear."

Pure functions. Explicit data. Deterministic flow.
No hidden mutation. No stack explosions. No OOP time paradoxes.

This config sends your codebase back to a cleaner timeline.

🧪 WHAT IT ENFORCES

⚛ Functional Discipline

• No class
• No this
• No throw
• No hidden state
• Data in → Data out

🧼 Strict Formatting

• Tabs only
• Unix line endings
• No trailing whitespace
• No padded blocks

🛡 TypeScript at Full Safety

• No any
• No unsafe calls
• No unsafe returns
• No unsafe member access

🚨 Explicit Error Channels

• Errors are values
• Failures travel as data
• No invisible control-flow jumps
• No surprise stack explosions

🌀 ERROR HANDLING — TIME SAFETY PROTOCOL

"A throw doesn't just fail your function, Marty… it rips it out of its timeline."

| 💥 DeLorean Crash (What NOT to do) | ⚡ Flux Capacitor Stable (How to do it) | |------------------------------------------|---------------------------------------------| | throw err; ❌ Timeline rupture | return err(reason); ✅ Time anchor | | | return ok(value); ✅ Deterministic | | • Control flow teleports | • Failure becomes data | | • Return types lie | • Control flow stays visible | | • Callers lose predictability | • Safe retry, branch, recover | | • Invisible stack explosions | • No hidden surprises |

🧭 Rule of the Time Machine

• throw → Timeline explosion
• Result<Ok, Err> → Checkpoint in time

🕰 PHILOSOPHY (DOC BROWN'S LAW)

"Your code must know where it came from, where it is now, and where it's going."

This config enforces: - Explicit inputs - Explicit outputs - Explicit failure - Zero temporal ambiguity

Nothing mutates silently.
Nothing explodes invisibly.
Nothing lies about what it returns.

🔌 INSTALLATION

npm install -D eslint eslint-back-to-the-fp

🚀 USAGE (FLAT CONFIG)

Create eslint.config.js:

import fpConfig from 'eslint-back-to-the-fp';

export default fpConfig;

Time circuits engaged.

👨‍🔬 WHO THIS IS FOR

For developers who want: - Predictable systems - Composable logic - Deterministic failure paths - Safe refactoring - Architecture enforced by tooling

Not for: - Heavy inheritance OOP - Exception-driven control flow - Implicit mutable state machines

📜 LICENSE

MIT --- Free to fork, modify, and send your code back to a better timeline.

⚡ FINAL TRANSMISSION

"OOPs? Where we're going, we don't need OOPs. We have pure functions."

Destination: Clean Code Era
Energy: 1.21 Gigawatts ⚡
Status: Flux Capacitor Engaged