@goab/roastr

v1.0.8

Published

4 months ago

A hilarious console debugging roaster that turns every console.log(), error, and warning into Rick & Morty roasts for developers

0High
0Medium
0Low

itachi1

error debug roast rick-morty console fetch logging

🧪 Roastr

"Listen up, you code-writing mouth-breathers!" - Rick

"Aw jeez, Rick, maybe we should be nicer to the developers..." - Morty

Rick: "Wubba lubba dub dub! So you losers are tired of your boring, personality-free console logs? Well congratulations, you've stumbled upon the universe's most advanced debugging roasting system! I've literally built interdimensional cable networks with more enthusiasm than your average console.log() statement."

Morty: "Um, what Rick's trying to say is... Roastr makes debugging more fun! It, uh, it adds Rick and Morty characters to your console methods, so instead of boring logs, you get... well, you get roasted. But in a good way! I think?"

Rick: "Shut up Morty! burp Look, I've seen more sophisticated debugging in Jerry's browser history. This package wraps EVERY console method - log, error, warn, info, debug, trace, table, group, time, count, assert - with personality that actually makes sense. Unlike your code."

🚀 Installation

Rick: "Even Jerry could install this. Probably."

npm install @goab/roastr

Morty: "Aw geez, that's actually pretty easy! Even I could remember that command!"

🎮 Quick Start

Rick: "Alright, pay attention because I'm only explaining this once, unlike your code which I'll have to explain is terrible multiple times:"

import { initRoastr } from "@goab/roastr";

// Choose your tormentor... I mean, debugging companion
initRoastr("Rick");

console.log("Testing my API");
// Rick: "Oh great, another genius using console.log(). Let me guess, you also think JavaScript is a 'real' programming language:"

Morty: "Oh! Oh! And if you want me to help instead of Rick being all... Rick-y, you can do this:"

initRoastr("Morty");

console.error("Database connection failed");
// Morty: "Oh no, an error! This is bad, right? This seems really bad! Here's what went wrong:"

Rick: "Or if you're boring and have no sense of humor whatsoever:"

initRoastr("Default");
// Gets you vanilla, personality-free messages. Ugh.

🧠 Using Roastr in Next.js

Rick: "Listen up, Next.js users! Since your fancy layouts are server components by default, you need to run my brilliant roasting system on the client side. Don't screw this up."

Morty: "Um, what Rick means is... since Next.js layouts are server components by default, you need to run Roastr on the client side. To do this, wrap initRoastr inside a useEffect in a client component."

1. Create a client component:

// components/RoastrInit.tsx
"use client";
import { useEffect } from "react";
import { initRoastr } from "@goab/roastr";

export default function RoastrInit() {
  useEffect(() => {
    initRoastr("Morty"); // Choose your character
  }, []);

  return null;
}

2. Add it to your layout.tsx:

// app/layout.tsx
import RoastrInit from "@/components/RoastrInit";

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        <RoastrInit />
        {children}
      </body>
    </html>
  );
}

Rick: "Now every console.log, console.warn, or console.error will be roasted globally. You're welcome for making your debugging infinitely more entertaining."

Morty: "Aw jeez, that's actually pretty cool! Now Rick and I will be there for all your debugging adventures!"

🎭 Meet Your New Debugging Partners

🧪 Rick Sanchez - Chief Science Officer of Brutal Honesty

Rick: "I'm gonna be straight with you - your debugging skills are more primitive than Jerry's understanding of quantum physics. I'll roast every console method you use while actually making your debugging experience infinitely better. It's called 'tough love,' look it up."

Sample Rick Roast:

"console.log() again? I've built civilizations that debug better than whatever this pathetic excuse for code inspection is:"

😰 Morty Smith - Anxious Assistant Developer

Morty: "H-Hey! I try to be supportive, you know? I just... I get really worried about your code sometimes. Like, what if the warnings are serious? What if the errors mean something really bad is happening? I-I just want to help, but I also don't want anything to explode..."

Sample Morty Support:

"Aw jeez, another console.log()? Rick's gonna be so mad about this debugging approach. But here it is:"

🔧 Every Console Method Gets the Rick & Morty Treatment

Rick: "Unlike most packages created by bootcamp graduates, this one actually WORKS with every console method. Observe:"

| Method | Rick's Approach | Morty's Approach | | ----------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | | console.log() | "Still using console.log()? Even Mr. Meeseeks would find a better solution" | "Aw jeez, console.log() again? I-I guess that's okay..." | | console.error() | "ERROR?! I'm not surprised. Your programming skills are worse than Jerry's self-esteem" | "Oh no, an error! Should I be worried? This looks pretty serious" | | console.warn() | "A warning? Your entire codebase is a warning waiting to happen" | "A warning? Oh geez, that sounds concerning! Should we be worried?" | | console.info() | "console.info()? What's next, gonna send me a newsletter?" | "console.info()? Oh, that's nice! Information is good, right?" | | console.debug() | "At least you're trying to debug instead of just hoping it works" | "Debugging? Oh good, that means we're trying to fix things!" |

Morty: "And, um, Rick made it work with like... ALL the console methods! Even the scary ones like console.trace() and console.assert()!"

Rick: "That's right Morty! Because unlike your typical npm package that does one thing poorly, this does EVERYTHING excellently. burp"

🛠️ Advanced Features (Because You'll Need Them)

Character Switching Mid-Session

Rick: "Changed your mind? Typical. Here's how you switch characters without breaking everything:"

// Start with my superior intellect
initRoastr("Rick");
console.log("Rick mode activated");

// Switch to Morty if you can't handle the truth
initRoastr("Morty");
console.log("Now in anxiety mode");

Morty: "Oh! And if you need to go back to boring console logs for some reason:"

import { restoreConsole } from "@goab/roastr";

restoreConsole(); // Back to soul-crushing normalcy

🎯 Why You Need This (Spoiler: You Do)

Rick: "Look, your debugging is already a joke - at least now it's an INTENTIONAL joke. Here's why this package is infinitely better than your current approach:"

🔥 Educational Roasting: Learn better debugging habits through public humiliation
🎭 Personality: Your console finally has more personality than Jerry
⚡ Zero Performance Impact: Unlike your code, this doesn't slow anything down
🧪 Complete Coverage: Every console method, because I don't do half-measures
📦 TypeScript Support: Fully typed, because even I have standards

Morty: "Plus, um, it actually makes debugging kind of fun? Like, even when things go wrong, at least Rick and I are there to... well, Rick roasts you and I worry about everything, but we're there!"

🚨 Production Usage Warning

Rick: "Obviously don't use this in production, genius. Your users don't need to know how incompetent you are:"

if (process.env.NODE_ENV === "development") {
  initRoastr("Rick"); // For development masochism
}

Morty: "Yeah, uh, Rick's right. We should probably keep the roasting between us developers, you know?"

🤝 Contributing

Rick: "Found a bug? Want to add more roasts? Fine, whatever. Just don't submit garbage code:"

Fork the repo (try not to break it)
Create your feature branch
Add your roasts (make them good, unlike your debugging skills)
Submit a pull request (I'll probably reject it anyway)

Morty: "Rick! Be nice! Um, we actually really appreciate contributions! Every little bit helps make the package better!"

📊 Package Stats That'll Blow Your Tiny Mind

Rick: "Over 220 unique roasts PER console method PER character. That's more variety than your entire programming toolkit."

Morty: "That's... that's actually a lot of roasts, Rick. Like, maybe too many? Is that okay? Should we be worried about roast overflow?"

Rick: "Shut up Morty! Quality AND quantity - concepts foreign to most developers."

🎪 Side Effects (All Good Ones)

Rick: "Warning: May cause excessive laughter, improved coding habits, and existential crises about your career choices."

Morty: "Oh! And, um, you might actually start debugging better because you don't want Rick to roast you as much!"

Rick: "Exactly! It's called 'negative reinforcement learning,' Morty. Though in this case, it's more like 'reality reinforcement learning.'"

📜 License

Rick: "MIT License - use it, abuse it, get roasted by it. Just like everything else in your programming career."

Morty: "The license is really nice! Very permissive! Rick spent like, five seconds picking it!"

🎬 Final Words

Rick: "Look, this package won't fix your terrible code architecture or your questionable life choices, but at least now your debugging sessions will be entertaining. And hey, maybe if you get roasted enough, you'll actually learn something. Stranger things have happened. burp"

Morty: "Aw jeez, Rick, maybe end on a nicer note? Um... we really hope this helps make your coding more fun! And, uh, try not to take Rick's roasts too personally. He means well! I think!"

Rick: "I absolutely do not mean well, Morty. I mean accurately."

"Wubba lubba dub dub! Now stop reading documentation and go get roasted!" - Rick

"Good luck with your debugging! We're rooting for you!" - Morty