Perf tip: if your web app ships large JSON-like configuration as JavaScript object literals, consider using JSON.parse instead. It’s much faster, especially for cold loads! https://v8.dev/blog/cost-of-javascript-2019#json …pic.twitter.com/p0WICUm7zx
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Would this be generated by a build step?
Yeah, bundlers and other tools that produce JS can add heuristics that cleverly decide which approach to use (depending on the size of the object, for example). Developers definitely shouldn’t worry about this to the extent that they’d write JSON.parse("…") by hand!
Genuinely didn't know there was another way than writing JS by hand?
Well, not JS, I mean the JSON representation of the object. But I don’t write JS code by hand either. Only Typescript 
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.