Bug: TS compilation error because of missing URL type

When using applicationinsights latest package ( 2.1.4 ) in TS projects which target Node only (no browser), I get the following compilation error:

node_modules/applicationinsights/out/Declarations/Contracts/TelemetryTypes/NodeHttpDependencyTelemetry.d.ts:12:23 - error TS2304: Cannot find name 'URL'.

12     options: string | URL | http.RequestOptions | https.RequestOptions;
                         ~~~

Probably you guys are missing some module import?

Very dirty workaround: I found similar error (in different NPM package): https://github.com/DefinitelyTyped/DefinitelyTyped/issues/19799 . It suggested adding dom library as workaround. Of course, doing this for your Node project has all kinds of nasty implications, which is why I just downgraded to 1.8.10.

[jasonzuvela-wywm]

I resolved this for myself by adding DOM to the tsconfig lib array:

tsconfig.json

{
  "compilerOptions": {
    ...
    "lib": [
      "esnext",
      "DOM" <-- this
    ],
}

It then compiled fine.

[stazz]

Long time no see! My vacation started pretty quickly after my last comment, and then I got swamped with other things. But, I found out solution that doesn’t need PR to this repo.

If you are running backend stuff, and definitely don’t want to include DOM TS library (to avoid runtime crashes which pass TS typechecks), another option is to use approach explained in @microsoft/microsoft-graph-client library:

First, install some fetch library for Node, e.g. cross-fetch:

  "dependencies": {
    "applicationinsights": "2.1.8",
    "cross-fetch": "3.1.4"
  },

Then, in your TS code, just import fetch library stuff before using "applicationinsights":

// As per instructions from https://docs.microsoft.com/en-us/azure/azure-monitor/app/nodejs
// Load the Application Insights library ,require("applicationinsights"), as early as possible in your scripts before loading other packages.
import "cross-fetch";
import "cross-fetch/polyfill";
import * as appInsights from "applicationinsights";
import { env } from "process";
const instrumentationKey = env.APPINSIGHTS_INSTRUMENTATIONKEY;
if (instrumentationKey) {
  appInsights
    .setup(instrumentationKey)
    .setSendLiveMetrics(true)
    .setAutoCollectConsole(true, true)
    .setAutoDependencyCorrelation(true)
    .start();
}

Now, the tsc will succeed without errors (make sure to have moduleResolution compiler config field set to node), and without DOM library:

$ npm run tsc

> your-project@1.0.0 tsc
> tsc --project tsconfig.json