codex-team/editor.js

[Bug] Polyfill promise conflict

Open

#1,634 opened on Apr 8, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (26,602 stars) (1,985 forks)batch import
buggood first issue

Description

This package seems to polyfill window.Promise, regardless of whether window.Promise already exists. This is causing problems as we are using and relying on our own polyfill (bluebird.js), but this is being replaced if I call new EditorJS().

Contributor guide

Tech stack
typescriptjavascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of polyfillsFamiliarity with Promise
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue reports that Editor.js polyfills window.Promise unconditionally, overriding existing polyfills like Bluebird. To resolve, locate the polyfill code in the repository (likely in a polyfill or entry file, e.g., src/index.ts or a webpack config). Consider conditionally attaching the polyfill only if window.Promise is undefined. Check if there are any comments or linked PRs for guidance; the issue has no activity, so the fix should be straightforward once the polyfill source is identified.