Skip to content

Conversation

Copy link

Copilot AI commented Nov 7, 2025

UI fails to load with TypeError: Accessor not expected at intrinsics.%IteratorPrototype%.constructor due to ses incompatibility with JavaScript iterator helpers.

Changes

  • Bump ses from 1.8.0 to 1.14.0 in root package.json resolutions
  • Bump ses from ^1.8.0 to ^1.14.0 in ui/package.json devDependencies
  • Update yarn.lock with new ses dependencies (@endo/cache-map, @endo/[email protected], @endo/immutable-arraybuffer)

Version 1.14.0 includes fixes for iterator helper compatibility that resolve the lockdown initialization error.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • download.cypress.io
    • Triggering command: /usr/local/bin/node index.js --exec install (dns block)
  • edgedl.me.gvt1.com
    • Triggering command: /usr/local/bin/node install.mjs (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>UI error probably link to a use of a deprecated version of ses</issue_title>
<issue_description>Going through the video tutorial associated to the dapp, I manage to go through up until the launching of the dapp with yarn start:ui. The dapp is launched and open on localhost on port 5473 but the the browser displays a blank page and I get the following errors in the console:

Image

The details of the error is:

TypeError: Accessor not expected at intrinsics.%IteratorPrototype%.constructor    isAllowedProperty ses.js:2173
    visitProperties ses.js:2202
    isAllowedPropertyValue ses.js:2134
    isAllowedProperty ses.js:2170
    visitProperties ses.js:2202
    whitelistIntrinsics ses.js:2226
    repairIntrinsics ses.js:5277
    lockdown ses.js:5319
    <anonymous> installSesLockdown.ts:7
[ses.js:3662:18](http://localhost:5173/node_modules/.vite/deps/ses.js?v=9acd1c0f)    tameConsole ses.js:3662
    (Asynchrone : EventListener.handleEvent)
    tameConsole ses.js:3660
    repairIntrinsics ses.js:5265
    lockdown ses.js:5319
    <anonyme> installSesLockdown.ts:7
  • Do you have ideas where this could come from?

I personally looked at the ses (hardened javascript) dependency and it seems that we are using a deprecated version (0.18.8) according to the npm package webpage: "Please upgrade to ses@^1.1.0. Version 0.18.8 breaks in the presence of the new JavaScript iterator helpers."
I believe the issue might come from there. 

I then had a bit of struggle to completely remove the use of deprecated ses instance in dependencies and sub dependencies of the project. I tried to use resolutions but I am not sure this is working perfectly.  

  • Do you think this deprecated ses version could be the issue? If so, how to completely get rid of deprecated subdependencies use?</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Fix UI error linked to deprecated ses version Upgrade ses to 1.14.0 to fix iterator helpers incompatibility Nov 7, 2025
Copilot AI requested a review from dckc November 7, 2025 18:52
Copilot finished work on behalf of dckc November 7, 2025 18:52
@dckc dckc requested a review from kriskowal November 8, 2025 02:10
@dckc dckc marked this pull request as ready for review December 3, 2025 00:56
@dckc dckc enabled auto-merge December 3, 2025 00:56
Copy link
Member

@dckc dckc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

e2e tests are failing in ci; it's not obvious to me why

investigating is well below other priorities for me just now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UI error probably link to a use of a deprecated version of ses

3 participants