apollo-client does require process.env to be set since 2.4
See original GitHub issueIntended outcome: I wanted to use the apollo-client library for grapqhl requests in my nativescript application.
Actual outcome: The code failed, since no apollo-client was instanciated. After debugging, we found out that the code references the non existing variable process.env.NODE_ENV multiple times.
How to reproduce the issue: Create a nativescript app and add the apollo client with version 2.5 and up.
Versions
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Migrating to Apollo Server 4 - Apollo GraphQL Docs
In Apollo Server 3, immediately after constructing each DataSource subclass, Apollo Server invokes the dataSource.initialize({ cache, context }) function on ...
Read more >Migrating to Apollo Client 3.0 - Apollo GraphQL Docs
This article walks you through migrating your application to Apollo Client 3.0 from previous versions of Apollo Client. To illustrate the migration process, ......
Read more >Advanced HTTP networking - Apollo GraphQL Docs
Take full network control with Apollo Link. The Apollo Link library gives you fine-grained control of HTTP requests that are sent by Apollo...
Read more >Setting up Apollo Client | Full-Stack Quickstart
Apollo Client is view-layer agnostic, so you can use it with any of your favorite view layers such ... The ApolloClient constructor requires...
Read more >@apollo/client | Yarn - Package Manager
Apollo Client is a fully-featured caching GraphQL client with integrations for React, Angular, and more. It allows you to easily build UI components...
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 FreeTop 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
Top GitHub Comments
I believe this is something we can fix by polyfilling
process
in thets-invariant
package. It’s definitely not a concern that anyone using the Apollo Client libraries should have to worry about. Sorry for the annoyance!@uhoh-itsmaciek I’m happy to help. Can you open another issue and ping me so this doesn’t get lost in the weeds? Also if you have a screenshot of the stack trace that would be incredibly helpful.