21ee8527c7
* feat(typings): create environment package to provide strict type checking for process.env * feat(tools): add new 'environment' global type to migration generator * fixup! feat(typings): create environment package to provide strict type checking for process.env * fixup! fixup! feat(typings): create environment package to provide strict type checking for process.env * fixup! feat(tools): add new 'environment' global type to migration generator * chore(typings): use solution config file to proerly check extensions/declaration without leaking globals * feat(typings): make environment globals work everywhere with proper DX |
||
|---|---|---|
| .. | ||
| README.md | ||
| index.d.ts | ||
| tsconfig.json | ||
README.md
custom-global
usage
As of writing, the custom-global type package only provides IE 11-compatible definitions of Map/Set/WeakMap.
Adding definitions to this type package should be a last resort; in general, changing the lib option in
tsconfig.json is a better approach (the IE 11-compatible types aren't available as a lib option).
The custom-global types are not referenced by default in most projects. To add a reference, add the following
to tsconfig.json compilerOptions:
"typeRoots": ["../../node_modules/@types", "../../typings"],
"types": ["custom-global"] // and any other types you reference