question-mark
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.

Error after updating to 1.1.0

See original GitHub issue

On building with typescript, this error message is presented error TS2339: Property 'createResolver' does not exist on type '(root: any, args?: {}, context?: {}) => Promise<any>'. Is there anything that needs to be updated? I’ve reverted to 1.0.3 for now

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:2
  • Comments:17 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
mringercommented, May 9, 2018

OK it appears that this error is caused when the necessary built in type declarations are not provided to tsc. They should to be explicitly linked either in the tsconfig.json or by passing the --lib flag to tsc.

Like so:

tsc index.ts --lib es6

or configuring your lib and target in your tsconfig.json

"compilerOptions": {
    "target": "es5",
    "lib": ["es6"],
    ...
}

More info here, here and here

Closing this unless there are further questions.

0reactions
theGlenncommented, May 31, 2018

@thebigredgeek @corydeppen I proposed the pull request #33 10 days ago to add concrete types.

TSC inferring is limited because libraries are expected to manually export the right custom interfaces and classes or provide an index.d.ts. Rewriting the library in TS without actually using concretes types definition seems pretty odd to me 🤔.

@mringer I’m not sure leaving users configuration define types exports interpretation is the way to go…

Read more comments on GitHub >

github_iconTop Results From Across the Web

Help with Latest Pokemon scarlet update 1.1.0 : r/SwitchPirates
Im trying to just install the update using Awoo and Goldleaf ive never ... 1.1.0 for scarlet doesn't show in Awoo and gives...
Read more >
Getting DynamicContext error after upgrading to Karate 1.1.0 ...
Hi, I am getting "DynamicContext could not be passed from one context to another" error message after upgrading to Karate 1.1.0 from 1.1.0....
Read more >
Error after upgrade to 1.1.0 - Flarum Community
Hi, users are unable to log into the forum after the upgrade. They get the following message: Oops! Something went wrong.
Read more >
Upgrade from Jetpack Compose 1.0.5 to 1.1.0 - Stack Overflow
It builds with no errors and no warnings. However, it does not launch anymore. Problems Tab in Android Studio indicates that are 104...
Read more >
PHP 8.1 psr vendor directory error – must update to 1.1.0
WooCommerce throws a fatal error when used with any other theme that uses a more up to date version of /vender/psr/container.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found