-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strict mode in core-js
errors in Zotero 6
#319
Comments
Maybe it's related to the fact that the According to dev docs (emphasis added):
The bundled JS currently starts as follows: if (!Zotero.Notero) {
// Make timer functions globally available in Zotero 6
if (typeof setTimeout === 'undefined') {
var setTimeout = Zotero.setTimeout;
}
if (typeof clearTimeout === 'undefined') {
var clearTimeout = Zotero.clearTimeout;
}
"use strict";
(() => {
var __create = Object.create;
var __defProp = Object.defineProperty; |
dvanoni
added a commit
that referenced
this issue
Jan 1, 2024
dvanoni
added a commit
that referenced
this issue
Jan 1, 2024
* refactor: Replace `Object.fromEntries` polyfill with patch * refactor: Replace `core-js` with `core-js-pure` to avoid pollution Closes #319 * build: Add schema definitions for JSON config files * build: Remove unused `esbuild.js` entry from `.eslintignore` * refactor: Format xhtml and xul files with Prettier * feat: Support observing changes to Notero prefs * feat: Replace Notion database ID text field with selection menu * docs(README): Remove step about copying database ID * docs(README): Remove FAQ about invalid request URL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a follow-up to #317:
core-js
v3.32.0 causes an error in Zotero 6Resources
The text was updated successfully, but these errors were encountered: