Apollo-client-devtools: Latest update breaks youtube.com

Created on 15 Mar 2021  ·  9Comments  ·  Source: apollographql/apollo-client-devtools

Intended outcome:

youtube.com loads successfully.

Actual outcome:

youtube.com scripts failed to load when the apollo extension is turn on, with the error:
Uncaught TypeError: Cannot assign to read only property 'process' of object '#<Window>'
It seems that the apollo extension sets the window.process to a readonly property and the youtube script tries to set it again.

How to reproduce the issue:

  • Install the apollo chrome extension
  • Go to youtube.com

Desktop (please complete the following information):

  • OS: [e.g. iOS] MacOS
  • Browser [e.g. chrome, safari] Chrome
  • Browser version [e.g. 22] 89
  • Extension version [e.g. 3.0] 3.0.0
🐞 bug

Most helpful comment

Apollo Client Devtools 3.0.1 has been submitted for review; 🤞it will be available shortly.

All 9 comments

Same here,

Extension version: 3.0.0
OS: Windows 10 64bit,
Browser: Chrome v89.0.4389.90

Having the same issue

Extension version: 3.0.0
OS: Windows 10 OS Version 2009 (Build 19042.867)
Browser: Edge 89.0.774.54 (Official build) (64-bit)

I'm also experiencing this issue, refreshing the page seems to get past the initial error. Hard refresh causes it to appear again.

Extension version: 3.0.0
OS: Arch linux 5.11.6-arch1-1
Browser: Chromium 89.0.4389.90

Yikes - I'll take a look. Thanks all!

The culprit seems to be Apollo Client's ts-invariant dependency, which is locking process: https://github.com/apollographql/invariant-packages/blob/68796f8a7c3d36338402ff1280dd9dfff38db521/packages/ts-invariant/src/invariant.ts#L68-L70

We're working on a fix.

Same problem here. It also broke my Meteor app (but only since the latest Chrome update).

Fixed in https://github.com/apollographql/apollo-client-devtools/pull/460, but re-opening until the new version is published.

Apollo Client Devtools 3.0.1 has been submitted for review; 🤞it will be available shortly.

3.0.1 should be available now - let me know if this issue still occurs. Thanks!

Was this page helpful?
0 / 5 - 0 ratings