Polyfill Array.at() for Qt5 compatibility#501
Merged
jitseniesen merged 4 commits intospyder-ide:masterfrom Oct 15, 2025
Merged
Conversation
Following Jupyter notebook PR #7735.
This is to follow Jupyter which also uses react version 18.2.0.
Follows Jupter notebook PR #7198 which was part of Jupyter notebook version 7.1. This elimiates the "plugin xxx is already registered" error messages.
jitseniesen
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The internal console shows the error message
Probably related to this, markdown cells are not displayed correctly.
This looks to be related to issue markedjs/marked#3546, which is about the member function
at()of the (standard library?) classArray. Apparently, this function is only defined in Chrome 92, but Spyder includes Qt WebEngine 5.15.15 which is based on Chromium 87. One fix would be to update to at least WebEngine 6.2.5 but that needs us to package Qt6 WebEngine.This PR includes another fix: it uses a polyfill from core-js to define the missing function (if I understand everything correctly). This does seem to resolve the markdown issue. Additionally, the PR syncs some versions of JavaScript libraries to eliminate more warnings in the internal console.
Fixes #500.