NPM Release

[smkhalsa]

The last NPM release was ~5 years ago. Any chance we can get a new release so we don't have to point to specific commits?

[mpetroff]

A release will happen as soon as I'm able to find the time to do the necessary QA and testing. However, at this point, I know better than to try to make an estimate for when that will be, since I've made and failed to meet such estimates several times now. Sorry I can't say anything more definitive.

[StigNygaard]

Maybe lower the ambitions regarding (fully tested) browser compatibility?

I say IE11 is not relevant anymore. To keep compatibility with Windows 7-8.1 (and MacOS 10.12-10.14) users, test with Firefox 115(*) and Chrome 109 based browsers.
Maybe keep older browsers as "assumed to work", but not thoroughly tested?

(*) At least for a few months more, Mozilla are still releasing security updates for Firefox ESR 115.x.

[mpetroff]

Maybe keep older browsers as "assumed to work", but not thoroughly tested?

That's already the case; the browser compatibility section mentions that "only recent browsers are tested." I agree that it makes sense to completely drop IE from the list, though.

The biggest issue has generally been testing with Safari. I recently gained access to an up-to-date macOS machine after several years of not having one (my newest Macbook is several years out of support), so I can finally test with both desktop and mobile Safari again.

I also need to fix CI and switch it from Travis to GitHub Actions (assuming I can get headless WebGL working, which tends to be challenging).

[neuhaus]

Thanks @mpetroff - looking forward to a release!

[eyecatchup]

Half a year later, nothing happened. And we've already been there years ago, right?

• (NPM) Release plans #1102
• New Release #1129

I doubt, at this point, a new release is ever gonna happen. Sad. And, to be honest, really can't understand your communication strategy, @mpetroff.

[neuhaus]

This is such a nice piece of software. Bummer.
@mpetroff let us know it we can help