this post was submitted on 03 Sep 2024
845 points (99.4% liked)
Programmer Humor
32555 readers
480 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just run your prod env in debug mode! Problem solved.
Lol my workplace ships Angular in debug mode. Don't worry though, the whole page kills itself if a dubious third-party library detects the console is open. Very secure and not brittle at all! ~~Please send help~~
Blink-blink-blink. Blink. Blink. Blink. Blink-blink-blink.
No, I don't have something in my eyes, I swear I'm fine looks nervously at boss.
Hang tight help is on the way.
Now I'm curious how this detection would work.
I've seen some that activate an insane number of breakpoints, so that the page freezes when the dev tools open. Although Firefox let's you disable breaking on breakpoints all together, so it only really stops those that don't know what they're doing.
You can imagine how many node projects there are running in production with
npm run
. I have encountered js/ts/node devs that don't even know that you should like, build your project, withnpm build
and then ship and serve the bundle.I just died a little inside. Thank you.
i have absolutely seen multiple projects on github that specifically tell you to do "npm run" as part of deploying it.