You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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
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.
The text was updated successfully, but these errors were encountered: