Hacker GitHub

← All repos

niutech/jxl.js

View on GitHub ↗ ★ 364 JavaScript

JPEG XL decoder in JavaScript using WebAssembly (WASM)

19 mentions on Hacker News by 12 people: 1 story, 18 comments · first 2022-11-22 · latest 2025-08-19

Mentions per year 19 mentions · busiest year 2023 (9)
20082026
  1. …could use it for new image formats and the like as well. There are things like JXL.js that do this: https://github.com/niutech/jxl.js
    comment by JimDabell · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  2. > but there is one serious seemingly insurmountable obstacle It can be surmounted with WebAssembly: https://github.com/niutech/jxl.js/ Single thread demo: https://niutech.github.io/jxl.js/ Multithread demo:…
  3. …team is ending up as a gatekeeper of the Internet by pick and choosing what gets developed or not. https://github.com/niutech/jxl.js is based on Chromium tech (Squoosh from GoogleChromeLabs) and provides an opportunity to use JXL with no…
    comment by pgeorgi · 2024-03-01 · in JPEG XL and the Pareto Front
  4. …images [1]. In the end I switched to a proxy server, that reencoded jxl images into png. [0]: https://github.com/niutech/jxl.js/issues/6 [1]: https://github.com/niutech/jxl.js/issues/7
    comment by 149765 · 2024-03-01 · in JPEG XL and the Pareto Front
  5. …or interest in using JXL in situations where they could. Where's the wide-spread use of jxl.js ( https://github.com/niutech/jxl.js ) to demonstrate that there are actual users desperate for native codec support? (aside: jxl.js is based on…
    comment by pgeorgi · 2024-03-01 · in JPEG XL and the Pareto Front
  6. https://github.com/niutech/jxl.js a javascript polyfill taken from the main page https://jpegxl.info/ There are other decoders [0] written in a "safe language" (rust) listed as well. So no there are many "safe" implementations [0]…
  7. You can use WASM for image codecs, like my JPEG XL decoder: https://github.com/niutech/jxl.js There is also WebCodecs API: https://developer.mozilla.org/en-US/docs/Web/API/WebCodecs_A...
    comment by niutech · 2023-09-14 · in Chrome: Heap buffer overflow in WebP
  8. My JPEG XL decoder uses WASM: https://github.com/niutech/jxl.js
    comment by niutech · 2023-09-14 · in Chrome: Heap buffer overflow in WebP
  9. …tag. Is this true if you provide a polyfill? Have you tried it and it failed? (Serious question.) https://github.com/niutech/jxl.js
  10. In the meantime you can use a polyfill: https://github.com/niutech/jxl.js
  11. and here's one: https://github.com/niutech/jxl.js
  12. …will be happy to learn that there's nothing preventing them from using it on their sites right now: https://github.com/niutech/jxl.js If you want Chrome to ship with JPEG-XL support, use it. At some point, browser makers will decide it's…
  13. …decoder to make the JPEG-XL images work for everyone. For example, here's a WebAssembly decoder: https://github.com/niutech/jxl.js Demo: https://niutech.github.io/jxl.js/
  14. …WebAssembly. It'd be lower performance than native decoding but probably not that bad. Here's one: https://github.com/niutech/jxl.js Demo: https://niutech.github.io/jxl.js/ Libjxl's own WASM build: https://github.com/libjxl/libjxl/tree/main…
    comment by clouddrover · 2023-03-06 · in JPEG XL vs. AVIF: A Comparison
  15. :) There are some wasm vs native benchmarks in the context of JPEG XL (for example https://github.com/niutech/jxl.js#benchmark ) Could also be interesting for you to run the vqsort benchmark: https://github.com/google/highway/blob/master/hw…
  16. Have a look at WASM decoder JXL.js: https://github.com/niutech/jxl.js
  17. This is what I did with JXL.js Multithread ( https://github.com/niutech/jxl.js#multithread-version ) - but instead of <canvas> I am pushing the blob to the <img>.
  18. …memory pressure is high. [1] https://developer.mozilla.org/en-US/docs/Web/API/CSS_Paintin... [2] https://github.com/niutech/jxl.js