Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unhandled Exception Error ReferenceError: fetch is not defined #1420

Closed
rpong opened this issue Jul 21, 2023 · 2 comments
Closed

Unhandled Exception Error ReferenceError: fetch is not defined #1420

rpong opened this issue Jul 21, 2023 · 2 comments
Assignees
Labels

Comments

@rpong
Copy link

rpong commented Jul 21, 2023

Describe the issue
We upgraded our Tracker from version 7.0.0 to 9.0.0.

And now we are getting this in our application:
Unhandled Exception Error ReferenceError: fetch is not defined

Steps to reproduce the issue

  1. Upgrade the Tracker version from 7.0.0 to 9.0.0
  2. Run the Application

Expected behavior
Application to run normally, without the Unhandled Exception Error ReferenceError: fetch is not defined Error

OpenReplay Environment
Frontend stack: Meteor JS
OpenReplay version:1.12.5
Tracker version: 9.0.0
Cloud provider: AWS

Additional context
We are on Node v14.21.3

Cannot find the documentation regarding the minimum Node Versions of the Tracker.

@rpong rpong added the bug Something isn't working label Jul 21, 2023
@estradino estradino assigned nick-delirium and unassigned estradino Jul 21, 2023
@estradino estradino added tracker and removed bug Something isn't working labels Jul 21, 2023
@nick-delirium
Copy link
Contributor

Tracker is intended to run only in the browser-like env, therefore for SSR apps you will need to ensure that you're initializing it on client side instead of server rendering phase.

If you're working on desktop app, or something that can only use nodejs api, let me know your use case and I'll think how can I fix the issue for you (maybe I'll just add a check that will skip fetch/xhr if it does not exist, but this will lead to loss of network capturing)

@rpong
Copy link
Author

rpong commented Jul 27, 2023

Thanks @nick-delirium for the clarification. We'll take care of this from our side.

@rpong rpong closed this as completed Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants