7

Random stuff that I’ve learned from a browser’s developer console

 2 years ago
source link: https://lihautan.com/random-stuff-i-learned-from-browser-console/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

Skip to content

Random stuff that I’ve learned from a browser’s developer console

On one normal day, I opened up my browser’s developer console for no reason. The page I was on, at that moment, was Facebook. And I saw a big red “Stop” in the console, and followed by a big bolded text of “This is a browser feature intended for developers….”.

fb

I paused for a while, amazed by what I’ve discovered randomly. This is quite interesting and I have two questions come up to my mind.

1. Is Facebook the only site that leaves message in the console?

It turns out to be NO. It’s not just Facebook.

This is what I found out after some random searches: Oculus and Coursera are hiring people through the console!

oc Oculus hiring people through the console

coursera Coursera did the same thing too!

It seems like this is a good place to hire web stack developer. Since the only person who is going to look into the console of your page is a web developer, or a full stack developer, hiring them through your console isn’t a bad idea after all.

3. So can the console print out images?

It’s a YES again. But how?

You can refer to this awesome console.image library developed by adriancooney. He will explain how he did it to you.

So, why not create an express middleware for this?

This was the random idea that came out from my mind after seeing websites leaving messages in the console. Why not have an express middleware that injects a script that prints to the console for each html pages served from the express server. It should have an simple intuitive API, and should not pollute to the global namespace at all.

So, this is what I’ve come up.

I know, the name is mouthful and awkward. This is because initially I intended the middleware to just print out a warning message. After a bit of consideration, turns out that hiring in the console should be a good use case too. But the name of the package just stuck there.

So, how do you use it?

It’s simple. See the code snippet below:

var express = require('express'),
        app = express(),
	hr = require('express-console-warning');
	
app.use(hr.LOG('Hello world')
	  .text('This is a blue text', {color: 'blue', fontSize: 'x-large'})
	  .text('and this is red', {color: 'red', fontSize: 'x-large'})
	  .image('http://memesvault.com/wp-content/uploads/Best-Meme-Faces-14.png',0.1)
	  .build());
app.use(express.static('client'));

And there you go.

express-console-warning

Disclaimer: I did not own the meme. I got the link from Google search just to try out the API.

Conclusion

So, these are what I’ve learned from a random action (open the developer console) and what I’ve created from it (express-console-warning).

express-console-warning github npm

Subscribe to my newsletter

Get the latest blog posts and project updates delivered right to your inbox

Powered by Buttondown.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK