Incorporating this adjustment into my tsconfig.json file has resulted in seamless execution without encountering any errors.

  "compilerOptions": {
    "target": "es5",
    "lib": ["es5", "es6", "dom"],  <--- this
    ...
  }

While unsure if the lib functionality pertains to Typescript 2.0 features, it appears that there are multiple libraries at our disposal.

Based on the typescript config schema (highlighting es2015.collection)

 "lib": {
      "description": "Specify library file to be included in the compilation. Requires TypeScript version 2.0 or later.",
      "type": "array",
      "items": {
        "type": "string",
        "enum": [ "es5", "es6", "es2015", "es7", "es2016", "es2017", "dom", "webworker", "scripthost", "es2015.core", "es2015.collection", "es2015.generator", "es2015.iterable",
                    "es2015.promise", "es2015.proxy", "es2015.reflect", "es2015.symbol", "es2015.symbol.wellknown", "es2016.array.include", "es2017.object", "es2017.sharedmemory" ]
      }
    }

This adjustment has addressed compile-time issues, but a lingering inquiry remains regarding why the tsc command executes error-free whereas webpack does not. Could it be that tsc automatically scans for all possible libraries regardless of the presence of lib declaration in tsconfig.json?

ES6 introduces new features like Map, Set, and Promise. Make sure your tsconfig.json file is configured correctly:

"target": "es5" 

When targeting es5, the compiler uses the standard es5 lib.d.ts, which may not include definitions for these ES6 types.

To access the definitions for these types, switch to using the lib.es6.d.ts:

"target": "es6" 

To enhance your code, simply include the following:

 "lib": ["es6"] // indicating at least ES6 compatibility

Keep the target unchanged. The target is crucial in instructing Typescript on which version of ECMAScript to compile your .ts files. You have the flexibility to modify it if the browser supporting your application will be compatible with that specific ECMAScript version.

As an illustration, I utilize "target": "es5" along with "lib": ["es6"].

One more reason might be:

Your .ts file does not fall under "rootDir": "./YourFolder",

If you're struggling to get any of these solutions to solve your issue, remember that if you explicitly mention the file you want to compile in the command line or package.json, TypeScript compiler (tsc) will ignore your tsconfig.json settings. To make it work, define the "files" and "outDir" in your tsconfig.json and try one of the suggested "lib" solutions. Afterwards, run the compilation with just:

tsc --sourcemaps

Use the following command line option if adding lib is not working in tsconfig.json: tsc index.ts --lib "es6"

If you encounter issues with including lib in tsconfig.json, consider utilizing the above-mentioned command line option.

To resolve the issue, I had to download and install the core-js typings using npm

npm install @types/core-js

clarification:
The purpose of @types npm packages is to acquire type definitions through npm. This functionality is a key aspect of TypeScript 2.0.

@types are intended to supersede existing tools like typings and tsd, although support for these will be maintained for a period.

After finding that the typical solution of adding "es6" to lib did not work for my situation, I realized it was due to a different issue. My problem arose from using an older version of node while having installed a newer version of "@types/node" via npm. To resolve the errors I was encountering when trying to use tsc, I uninstalled the newer node typing and replaced it with a specific version compatible with my installed node version (v9.11.1). This simple adjustment fixed the issue for me.

Visit this link for more information

npm install typings -g
typings install

An important reminder: the command above is deprecated in npm version 5.6.0! Please make sure to use npm install @types/core-js instead.

My current version of node.js is 10.16.3. I encountered an issue where the typescript compiler was not recognizing my tsconfig.json file.

I found three solutions that resolved the problem for me:

1. Using ts-node to compile and run the file
2. Adding

   tsc filename.ts --lib "es6", "dom"

   during compilation
3. Installing @types/node to enable error-free execution with tsc filename.ts

To fix this issue, update the specified settings in your tsconfig.json file.

"lib": [
      "es2018",
      "dom",
      "es5", 
      "es6"
    ],
"module": "es2015",
"target": "es6"

Next, execute the following command in your terminal.

npm install @types/es6-shim

PROBLEM SOLVED!

To update your tsconfig.json file, simply replace the value for "target" from "es5" to "es6"

The solution to this problem is quite simple - just include the map method in your TypeScript file by adding the following code:

import { map } from 'rxjs/operators';

In order to resolve the issue, I found that adding @types/node was the solution:

yarn add @types/node --dev

If you prefer using npm instead:

npm install @types/node --dev

Furthermore, it is recommended to include "es6" in the "lib" array of your tsconfig.json if you plan on utilizing features like "Map", "Set", or "Promise".

If you're working with ES6, consider using the following method:

tsc filename.ts --lib es2015