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
Why is Node core different from a userland package in this regard? You could just *not bother* and those packages would simply depend on an older version of Node. If you wish to use Node 10, obviously you'll need packages supporting it, as with any userland package.
This was tried through the "engines" field and nobody used it. It's the platform's job to keep userland running. You can't build an ecosystem if the foundations keep shifting.
I suspect this is the real issue...
Well the engines field solve nothing IMO. This is all about which APIs are injected into your app vs what you explicitly require. The engines field has all the same issues as peerDependencies.
The ecosystem issue is a fair argument - but it is one of "downsides of new major versions" in general, which would apply also to a hugely popular userland package.
No, cause a new major isn't automatically injected into dependents. This is massively important point.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
