They coincide in most cases, but they don't if there are series of consecutive uppercase letters as in "HTMLParser"

just a nit... make the values lower-case. They tend to be easier for users. --unhandled-rejections=error_on_gc

It also makes your code harder to follower because you are using SCREAMING_SNAKE_CASE instead of nice, readable methods.

STREAMS originated in Version 8 Research Unix, as Streams (not capitalized).

Notice that the HTML elements (BUTTON, DIV, etc.) are in CAPS. We know this is bending the standard Ruby style rules slightly, but we think it reads better this way.

Text labels can be written in sentence case, as long as the button is clearly distinguishable from elements around it.

CautionText labels need to be distinct from other elements. If the text label isn’t fully capitalized, it should use a different color, style, or layout from other text.

As was mentioned in the comments above, the material design spec for buttons specifies that the text should be uppercase, but you can easily override its CSS property: paper-button { text-transform: none; }

No, this is not specified. The spec even says that contained buttons can be in sentence case

Sentence case, e.g. ‘Next section’. I use sentence case for more ‘friendly’ or ‘conversational’ platforms.

Note: Yes, it is sentence case, and yes, there should be a full stop if it was true sentence case — but for the love of all things good and designy, please don’t add a full stop.

Choose sentence case or title case over uppercase. (This being said, Material Design does use buttons with uppercase labels.)

const TsconfigPathsPlugin = require('tsconfig-paths-webpack-plugin')

The only difference is that they’re named with camelCase like onClick, onFocus, onDragEnter instead of the all-lowercase names from HTML (onclick, onfocus, ondragenter).

MinIO (needs capital IO)

Also notice that the component name Nested is capitalised. This convention has been adopted to allow us to differentiate between user-defined components and regular HTML tags.

cross join lateral

Then I modeled the the contributing.md and development.md after bundler's files and they use uppercase for those and so I did.

When you need to proxy HTTPS traffic, the environment variable is upper case: HTTPS_PROXY

From the man pages The environment variables can be specified in lower case or upper case. The lower case version has precedence. http_proxy is an exception as it is only available in lower case. Using an environment variable to set the proxy has the same effect as using the --proxy option

All-capitalized letters are hard to read.