Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

@azure/core-tracing@1.0.1: Type alias 'Resolved' circularly references itself.

See original GitHub issue

@azure/core-tracing:
1.0.1:
nodejs
- v14.19.1:
typescript
- 3.9.10:

Describe the bug

tsc

node_modules/@azure/core-rest-pipeline/node_modules/@azure/core-tracing/types/core-tracing.d.ts:81:21 - error TS2456: Type alias 'Resolved' circularly references itself.

81 export declare type Resolved<T> = T extends {
                       ~~~~~~~~

node_modules/@azure/core-rest-pipeline/node_modules/@azure/core-tracing/types/core-tracing.d.ts:83:41 - error TS2315: Type 'Resolved' is not generic.

83 } ? F extends (value: infer V) => any ? Resolved<V> : never : T;
                                           ~~~~~~~~~~~

node_modules/@azure/core-rest-pipeline/node_modules/@azure/core-tracing/types/core-tracing.d.ts:131:212 - error TS2315: Type 'Resolved' is not generic.

131     }, Callback extends (updatedOptions: Options, span: Omit<TracingSpan, "end">) => ReturnType<Callback>>(name: string, operationOptions: Options

To Reproduce pacakge.json

{
  "name": "repro",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "build": "tsc",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@azure/core-rest-pipeline": "^1.8.1",
    "typescript": "^3.9.10"
  }
}

index.ts

import { Resolved } from "./node_modules/@azure/core-tracing"
let r: Resolved<string>;

tsconfigs.json

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
    "outDir": "dist",
    "rootDir": ".",
    "sourceMap": true,
    "strict": false
  }
}

npm install
npm run build

Expected behavior Project should build successfully.

Issue Analytics

State:
Created a year ago
Comments:5 (2 by maintainers)

Top GitHub Comments

4reactions

maorlegercommented, May 11, 2022

Hi @nmarinel and @hund030 - It looks like our Resolved type uses features that are available in TypeScript >= 4.1, specifically https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-1.html#recursive-conditional-types

We are looking into options for downleveling the types to support TypeScript 3.x but in the interim if you can use TypeScript 4.1 or later this error should be resolved.

3reactions

hund030commented, May 9, 2022

I just workaround this issue by adding