The road ahead for JSZip

[Stuk]

Hello everyone!

My time to take care of JSZip has been limited for the past few years, and indeed it has languished. Fortunately @jonkoops has stepped up and offered to help bring JSZip up to date!

Here is an outline of the things we have planned, in rough priority order.

Getting up to date

• Updating the CI configuration, to move from Travis to Github actions
• Moving off Saucelabs for in-browser testing, and using Playwright to test instead.
• Fixing the bundling, and moving to something like Rollup or Rolldown.
• Updating the release steps to be more automated.
• Triaging outstanding issues.
• Enable Github Discussions,
• Move any of issues that are actually questions/discussions there

Updating process

• Put in place an RC release process to allow userbase testing before releases.
• Update the website/documentation. Typos, maybe a better format
• Define a milestone on GitHub for the next major version, and collect any issues/breaking changes to include.

Moving forward, and longer term

• Triaging PRs, and deciding which ones to merge
• Updating the code to use modern JS features, such as class! (Use modern JavaScript syntax #946)
• Figuring out the future for https://github.com/Stuk/jszip-utils, either bringing into this repo or deprecating
• Migrating to Typescript, or at least JSDoc based Typescript.
• Figure out how JSZip can use CompressionStreams.

Call to action!

Here's how you can help:

• Take a look at open issues and PRs, vote on the important ones: help us prioritize and move JSZip forward
• Join GitHub Discussions: Ask questions, share ideas, and shape the future of JSZip
• Give us input on what you want to see, what JSZip can add, and also what we can stop supporting!