kiwix-js-pwa VS offline-plugin

WikiMed by Kiwix is now at v2.7.4. The packages for 64bit and 32bit Linux and Windows contain the October 2023 WikiMed English ZIM (mdwiki_en_all_maxi_2023-10), together with the changes in the CHANGELOG. The Electron app uses Electron v22.3.25.

Release packages for Ubuntu, Debian, Fedora, OpenSUSE, AppImage, Windows XP/Vista/7/8/10/11: https://github.com/kiwix/kiwix-js-windows/releases/tag/v2.5.0

The packages contain the March 2023 WikiMed English ZIM (mdwiki_en_all_maxi_2023-03), because there have been no new updated MDWiki ZIM archives since March, together with the changes in the CHANGELOG (also copied below). The Electron app uses Electron v22.3.8.

Release: https://github.com/kiwix/kiwix-js-windows/releases/tag/v2.4.6-Wikivoyage

See full changelog for fixes and updates.

For overall changelog, see https://github.com/kiwix/kiwix-js-windows/blob/main/CHANGELOG.md.

Please note that Zimit support in the PWA is experimental, and it may struggle with highly dynamic content. Any issues can be reported to me here. Kiwix devs will be working on standardized (and hopefully more universal) Zimit support across the range of apps, with dedicated developer focus planned for the end of May.

u/verrucagnome This fix is now released in v2.4.0: https://github.com/kiwix/kiwix-js-windows/releases/tag/v2.4.0 and the PWA https://pwa.kiwix.org (let it update to v2.4.0).

u/Nibb31 There's no need to run it in Docker, as you can compile the Electron versions on either Linux or Windows simply by cloning the Repo and running npm install --save-dev, then npm start to test, or npm run dist-linux (or dist-win), to make packages. See scripts in package.json. It uses electron-builder to build the apps, in case you're familiar with its CLI.

The packages contain the December 2022 WikiMed English ZIM (mdwiki_en_all_maxi_2022-12), together with the changes in the CHANGELOG. The Electron app uses Electron v18.3.15.

For example, you have a Progressive Web Application using Service Workers, written in Angular, then you have to create a service worker manifest based on your output files. We don’t have a solution for this on Meteor CLI natively. However, Webpack has a lot of community plugins such as OfflinePlugin , Workbox and many others for this problem as a solution. Just install them, and add to your webpack.config.js . Meteor-Webpack will handle it like you’re working on a pure Webpack project.

Since Omatsuri is a browser only application the only thing that we need from service worker is to cache assets and provide app shell. Offline plugin does exactly that, the only thing we need to do – add it to the production build in webpack config: