Jeremy Tuloup

Closing as `0.4.0` is now available: https://github.com/jupyterlite/jupyterlite/releases/tag/v0.4.0

At least the `setImmediate` issue mentioned in https://github.com/jupyterlite/jupyterlite/issues/944 is reproducible on CI: 

So the "Basic code execution" test seems to be passing:  Which is about executing the JavaScript notebook, with the JavaScript kernel also running in a web worker: https://github.com/jupyterlite/jupyterlite/blob/da9e9856ec343dcbfc54b3c1a1cc5e0c609f39e9/ui-tests/test/kernels.spec.ts#L15-L24 So...

For reference the PR to test `jupyterlite-xeus-python` on `webkit`: https://github.com/jupyterlite/xeus-python-kernel/pull/175

Thanks @nikolayivanovbg for the report. It looks very similar to this existing issue: https://github.com/jupyterlite/jupyterlite/issues/1272 Should we close this one in favor of https://github.com/jupyterlite/jupyterlite/issues/1272?

Thanks @savakarrohan. Maybe there should also be a CI job to make sure the `Dockerfile` continues working over time?

Just created the `0.2.x` branch: https://github.com/jupyterlite/jupyterlite/tree/0.2.x

> Is there a rough idea for 0.3.0 ETA, now that jupyterlab-4.1rc1 is out ? April 2024 ? Yes, we had listed a couple of items above that would have...

`0.3.0` has been released: https://github.com/jupyterlite/jupyterlite/releases/tag/v0.3.0

Need to do a bit more testing to make sure this actually has a real effect.