This is a bit awkward since TypeScript already defines its own thing called Iterator purely for type-checking. So due to this unfortunate name clash, TypeScript needs to introduce a separate type to describe these native/built-in iterable iterators.

The HTMLLabelElement.htmlFor property reflects the value of the for content property.

In the second pass, read the paper with greater care, butignore details such as proofs.

fetch: fetcher

Using as * adds a module to the root namespace, so no prefix is required, but those members are still locally scoped to the current document.

Using a user-defined network provides a scoped network in which only containers attached to that network are able to communicate.

Right, because those are the only 3 instances where new "scopes" are created, which means you're seeing data for (probably) the first time.

There is zero relationship between sirv.com and this module or its author.

So that you can insert variables in your code without worrying if they clash with existing variable names.

Why do I need a global variable? Is the global requirement from ES6 modules (I'd have thought modules would be in a functional scope) or rollup?

Yeah, I can see foo being different things in different places being undesirable.

The @const indicates that the value is read-only (i.e. it cannot be assigned to or mutated in an expression such as an event handler), and communicates, through its similarity to const in JavaScript, that it only applies to the current scope (i.e. the current block or element).

Some GitLab features can behave differently for each environment. For example, you can create a secret variable to be injected only into a production environment.