Spaces:
Configuration error
Configuration error
Download sessions/node_modules/decode-named-character-reference/index.dom.js from CPISTO/TARSTHENEXT: direct link, hf CLI and curl.
- Browser
- Download file 1.24 kB
-
https://huggingface.co/spaces/CPISTO/TARSTHENEXT/resolve/main/sessions/node_modules/decode-named-character-reference/index.dom.js
- Command line
-
hf download hf://spaces/CPISTO/TARSTHENEXT/sessions/node_modules/decode-named-character-reference/index.dom.js
-
curl -L -o index.dom.js https://huggingface.co/spaces/CPISTO/TARSTHENEXT/resolve/main/sessions/node_modules/decode-named-character-reference/index.dom.js
1.24 kB
| /// <reference lib="dom" /> | |
| /* global document */ | |
| const element = document.createElement('i') | |
| /** | |
| * @param {string} value | |
| * @returns {string | false} | |
| */ | |
| export function decodeNamedCharacterReference(value) { | |
| const characterReference = '&' + value + ';' | |
| element.innerHTML = characterReference | |
| const character = element.textContent | |
| // Some named character references do not require the closing semicolon | |
| // (`¬`, for instance), which leads to situations where parsing the assumed | |
| // named reference of `¬it;` will result in the string `¬it;`. | |
| // When we encounter a trailing semicolon after parsing, and the character | |
| // reference to decode was not a semicolon (`;`), we can assume that the | |
| // matching was not complete. | |
| if ( | |
| // @ts-expect-error: TypeScript is wrong that `textContent` on elements can | |
| // yield `null`. | |
| character.charCodeAt(character.length - 1) === 59 /* `;` */ && | |
| value !== 'semi' | |
| ) { | |
| return false | |
| } | |
| // If the decoded string is equal to the input, the character reference was | |
| // not valid. | |
| // @ts-expect-error: TypeScript is wrong that `textContent` on elements can | |
| // yield `null`. | |
| return character === characterReference ? false : character | |
| } | |