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
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.
The pupeteer version used in this repo is pretty only indeed. Will need some time to test upgrading to the latest version doesn't break anything though.
If this might help anyone else:
I had the same "Object reference chain is too long" error even though puppeteer is the latest (v5.5.0).
And after switching my Node.js to the LTS version (v15.5.1 -> v14.15.4, Windows) the test task completes successfully.
Most appropriate sub-area of p5.js?
Details about the bug:
Follow the instruction given here : https://p5js.org/contributor-docs/#/?id=development-process to install your project. When running
npm run grunt
you might see an error due to thepuppeeter
package. An unhandled promise chain which can cause troubles, maybe differents according to your nodejs version.The issue for the package has been notified here : Error: Protocol error (Runtime.callFunctionOn): Object reference chain is too long undefined puppeteer/puppeteer#2746. As I can see, this error has been removed since 2018, so I suppose that p5js import a old and deprecated package of puppeeter
It seems to be a blocking error for some users (https://discourse.processing.org/t/fatal-error-protocol-error-runtime-callfunctionon-object-reference-chain-is-too-long/25591) but not for me, because I do not have the latest version of nodejs.
The text was updated successfully, but these errors were encountered: