⚡ ElasticsearchBook.com is crafted by Jozef Sorocin and powered by:
If you've ever dabbled with frontend development, you're already familiar with the dev tools. They cover everything from debugging (incl. setting breakpoints), through XHR request inspection, to code flow analysis, and much more. On top of that, it's incredibly easy to inspect HTML nodes and interact with the DOM. These interactions happen through JavaScript which is exposed through the console. In other words, we have a fully featured NodeJS-like environment at our fingertips!
This environment does not necessarily have to interact with the website it's currently open on — I use it a lot for general tasks such as JSON array iteration, formatting, and copying:
Demonstrating the usage of the [map](<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map>)
, [join](<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/join>)
, [reduce](<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/reduce>)
, and [copy](<https://scottwhittaker.net/chrome-devtools/2016/02/29/chrome-devtools-copy-object.html>)
functions.
I use this site whenever I need to format / prettify / compactify / validate a JSON.
I strive to format the code in my StackOverflow answers as best I can and this JSON formatter has been instrumental in making them what they are 😉 .
Some of my applications dynamically generate Elasticsearch queries, which, when unfurled, are often thousands of lines long. I first prettify these queries and then use diffchecker.com to inspect their differences further.
As shortly touched upon a few chapter back, TurfJS.org is a terrific open source geo library for the browser — meaning it works nicely in actual frontend apps but also when prototyping (incl. fast prototyping the dev tools console).