is there an alternative REACT_APP_AWS_API_ENDPOINT ？
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
get-graphql-schema https://beta.api.uniswap.org/v1/graphql -j
FetchError: request to https://beta.api.uniswap.org/v1/graphql failed, reason: connect ETIMEDOUT 162.125.82.7:443
at ClientRequest.<anonymous> (/home/parallels/.nvm/versions/node/v14.21.1/lib/node_modules/get-graphql-schema/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (events.js:400:28)
at TLSSocket.socketErrorListener (_http_client.js:475:9)
at TLSSocket.emit (events.js:400:28)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT'
}
is there an alternative REACT_APP_AWS_API_ENDPOINT ？
What does REACT_APP_AWS_API_ENDPOINT mean？
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for REACT_APP_AWS_API_ENDPOINT and inspect the configuration or entry points that reference it. Compare that usage with the reported get-graphql-schema request, then document what the variable means and whether an alternative endpoint is supported; done means the endpoint guidance is clear and answers the timeout question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100