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 using 1.1.0 on Angular@5
See original GitHub issueWhen we upgrade to v1.1.0 from v1.0.1 on an Angular5 project we’re getting the following error using apollo.watchQuery:
ERROR TypeError: Object(...) is not a function
apollo.query works as expected
Issue Analytics
- State:
- Created 5 years ago
- Reactions:9
- Comments:15 (3 by maintainers)
Top Results From Across the Web
Error using 1.1.0 on Angular@5 · Issue #651
When we upgrade to v1.1.0 from v1.0.1 on an Angular5 project we're getting the following error using apollo.watchQuery: ERROR TypeError: ...
Read more >require-from-string@^1.1.0 Error installing any package ...
Cleared my cache; Reinstalled NPM / AngularCli. Running any NPM command will unfortunately result in this command, even the uninstall commands.
Read more >Unable to resolve dependency tree error in Angular while ...
To fix Unable to resolve dependency tree error in Angular while installing `npm` packages follow the below steps. 1.
Read more >angular/core
Angular - the core framework. Latest version: 15.0.4, last published: 12 days ago. Start using @angular/core in your project by running `npm ...
Read more >How to install a specific Angular version | by Riccardo Andreatta
In this article you will learn how to install a specific Angular version in your local machine with a simple “hack”
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If rxjs@6 is a new dependency, shouldn’t this be a major version increment instead of 1.1.0?
We use Ionic, which depends on RxJs 5.*. How can we still use Apollo in our Ionic 4.7 Projects?