💡 Workarounds with data bufs ❌ in development
| 📖️ Library | @jaisocx/charcode-converter |
🏷️ ver.: 1.4.2 |
| 🗓 Updated | Winter 2026 | Tue Jan 20 06:28:29 CET 2026 |
| 📐 Size | 🗂 Folder: 1200 KB | 📦 Tarball: _ KB | 📋 .js: 5 KB |
| ⚡ JS Engine | 🌐 Browser: ✅ yes | 🧭 Express: ❌ no | 🖥️ Console: ❌ no |
Workarounds with data bufs
the class enhances the ImprovedTemplateRenderer Javascript class’ performance, while rewriting and rendering templates, assigning the rendered templates by reference, and not copying each byte in the bytebuffer, when copying texts of datatype string by value.
For this purpose, to copy templates by reference, since this is needed many times, and when building the entire html of the rendered sites ui tool by the ImprovedTemplateRenderer, the templates and the rendered templates this class converts to byte buffers with charcodes, and then the templates are of the datatype array, and the arrays in browsers are copied via javascript by reference.
The lookup tables are for the workaround, when encoding and decoding very long texts, to make the lookup fast.
however the alphabets with tens thousands of chars, use for sure lot of hundreds KB in the RAM for these lookup tables, the lookup tables are the RAM, used by the sites surfer’s browser, when a sites surfer navigated to the .html page with js tools, these use the CharcodeConverter Javascript class.
in the src/index.ts and transpiled/ESNext/index.js and transpiled/CommonJS/index.js file, the central file in this npm package, the CharcodeConverter class is added to the browser’s window js class, and this js class can be seen in the browser’s developers console, when researching window class.
Have a nice day.
Elias, Software Architect of Jaisocx Company