fix: replace decode-entity.browser.js for Web Workers

[yoshi389111]

Hello.

I've found what appears to be a small bug, so I'd like to report it.

Problem

In textlint/editor, if a named entity reference (e.g. >) is entered, the error "document is not defined" occurs.

Numeric entity references, however, work fine.

Screen Shot:

Error message and Stacktrace:

Failed to parse text by plugin: @textlint/markdown
Please report this error with the content to plugin author.
ReferenceError: document is not defined
 at e.exports [as default] (https://textlint-editor.netlify.app/textlint-worker.js:34:60556)
 at f (https://textlint-editor.netlify.app/textlint-worker.js:34:20587)
 at A (https://textlint-editor.netlify.app/textlint-worker.js:66:49848)
 at D (https://textlint-editor.netlify.app/textlint-worker.js:66:49790)
 at Object.write (https://textlint-editor.netlify.app/textlint-worker.js:66:49398)
 at o (https://textlint-editor.netlify.app/textlint-worker.js:14:26192)
 at e.exports (https://textlint-editor.netlify.app/textlint-worker.js:14:27118)
 at e.exports (https://textlint-editor.netlify.app/textlint-worker.js:26:328)
 at e.exports (https://textlint-editor.netlify.app/textlint-worker.js:66:11445)
 at Parser (https://textlint-editor.netlify.app/textlint-worker.js:34:84643)

Source:

This error seems to originate from parse-entities. The latest version of parse-entities is 4.0.2, but textlint/editor currently uses 2.0.0, which appears to switch between the browser and non-browser versions.

textlint/editor imports the browser version of parse-entities, which depends on document. However, since textlint/editor runs the relevant code inside a Web Worker, document is not available, leading to the error.

Proposed Solution

Possible solutions could include:

• Use the non-browser version of parse-entities
• Upgrading to a newer version of parse-entities
• Switching to a different library

For this pull request, I modified src/compiler.ts in @textlint/script-compiler to use the non-browser version, and added a Webpack plugin configuration.

With this change, we confirmed that the error no longer occurs when entering named entity references. That said, we haven’t yet conducted extensive testing.