imba2-json-beautifier VS browserslist

Source code is in imba2-json-beautifier repository.

import stringify from "json-stringify-pretty-compact" tag app prop maxlen = 80 prop indent = 2 prop text = JSON.stringify({hello: "world"}) prop error def prettify try let json = JSON.parse(text) let spaces = Array.from({length: parseInt(indent)+1}).join(" ") text = stringify(json, {maxLength: parseInt(maxlen), indent: spaces}) catch e error = ""+e imba.commit() def clear_error error = null def upload(event) let file = event.target.files[0] return unless file let reader = new FileReader reader.onload = do |event| text = event.target.result error = nil imba.commit() reader.readAsText(file) "JSON Beautifier" if error error "Indent" "Max row length" "Prettify" css display: flex flex-direction: column align-items: center ff: sans header font-size: 64px text-align: center textarea min-width: 50vw margin-bottom: 10px .controls display: grid grid-row-gap: 5px margin: auto label grid-column: 1 input, button grid-column: 2 .error background-color: #fcc min-width: 50vw padding: 5px border: 1px solid #800 imba.mount

Enter fullscreen mode Exit fullscreen mode

This is a very straightforward translation.

We need to convert Error to String, as Imba 2 doesn't like putting Error objects directly in the output, but that's probably a good idea anyway.

Other than that, it's just minor syntactic changes.

By the way I wonder if any framework will ever offer good solution for the label for problem. Right now they inherently use globally scoped ids.

Source code

Source code is in imba2-json-beautifier repository.

You can also see the live version here.

Coming next

In the next episode we'll try to add Cypress tests to this app.

Not these days, where most people are using evergreen browsers and iOS users upgrade very quickly.

Take a look at the defaults for browserslist, for example:

https://browsersl.ist/#q=defaults

It just barely supports Safari 15, on iOS only, and that’s likely to go away imminently because it’s under 1% usage.

browserslist

We compile JS only for modern browsers. The list of default browsers in Next can be overridden in your browserslist.

In the latest versions of Next.js, targeting specific browsers or features is a breeze using the Browserslist configuration in your package.json file. The latest version of Next.js (v13) uses the following configuration by default:

For a more general answer to browser support, check out https://github.com/browserslist/browserslist. That seems to be standard tool to help you with that.

As someone else pointed out, you're overestimating Chrome/ium's market share.

Regardless, after the web.dev/baseline announcement, I looked at Browslerlist and one of our site's analytics and it is shocking how many people are not using the last two versions of evergreen browsers. There is a long tail of browser versions in those stats.

https://browsersl.ist

The way folks handle this in production is with browserslist, which lets you query on different things you want to support: https://github.com/browserslist/browserslist. This in turn tells other parts of your tooling what language features to transpile for production.

I imagine tools could be built on top of that which do what you’re asking too

# .browserslist.rc # Babel Preset configuration # -------------------------- # Defines web-browser compatibility parameters for Babel to transpile your JS code. # This configuration is used by babel.config.js. # More information in here. # https://github.com/browserslist/browserslist # Support browsers with a market share higher than 5% >10%