This repository was archived by the owner on Oct 12, 2022. It is now read-only.
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Description
While writing @typings I had to come up with a name for those non-external module definitions. I settled on ambient because it seemed intuitive, the TypeScript compiler would use it in error messages and all other "global"-like names are even more overloaded. However, there's one sentence with this interpretation that doesn't work in the handbook.
We call declarations that don't define an implementation "ambient".
So technically, does that mean even external module definitions are considered "ambient". Is there a better term we should adopt to explain external and non-external module definitions? Preferably something with less syllables and one word that can be used in CLI scripts.