The current version of tinysort.charorder.min.js causes the following TypeError (in Firefox 88.0):
Uncaught TypeError: j is undefined (tinysort.charorder.min.js:1:206)
The way I understand this is that Webpack moves the const declaration/initialization of allCharList into a var declaration/initialization below the function definition of prepare, in the assumption that the declaration is hoisted and everything should work. But JavaScript only hoists the declaration of the variable, not the initialization, which means that when allCharList.slice(0) is called, the variable exists, but is not yet initialized, resulting in the "is undefined" error above.
I don't quite know how to tell Webpack to not make this mistake (or whether newer versions of Webpack don't do this), but I'd assume separating declaration and initialization into distinct statements would work.
The current version of tinysort.charorder.min.js causes the following TypeError (in Firefox 88.0):
Uncaught TypeError: j is undefined (tinysort.charorder.min.js:1:206)The way I understand this is that Webpack moves the
constdeclaration/initialization of allCharList into avardeclaration/initialization below the function definition of prepare, in the assumption that the declaration is hoisted and everything should work. But JavaScript only hoists the declaration of the variable, not the initialization, which means that when allCharList.slice(0) is called, the variable exists, but is not yet initialized, resulting in the "is undefined" error above.I don't quite know how to tell Webpack to not make this mistake (or whether newer versions of Webpack don't do this), but I'd assume separating declaration and initialization into distinct statements would work.