ref: update the build system to use hatch and update dependency versions

[horw]

The Jupyter build system was outdated, so this kernel needs to be migrated to the Hatch build system, which supports shareable files. On the other hand, JupyterLite has been significantly updated, with many new features now available.

The base for this PR was https://github.com/jupyterlite/pyodide-kernel, as it seemed to have been updated quite recently. However, it's too complicated, which is where echo-kernel shines — it provides an easy, not-overwhelming template example.

How to Start Dev Server

nvm use
npm run setup:py
jlpm install
jlpm build
jupyter labextension develop . --overwrite
jupyter lite serve

Further Steps

• update Readme

Related

Closes #8

[horw]

I guess this file handlers.py isn't needed now?

[horw]

@jtpio Hello!
What do you think about this migration? Any advice or suggestions for further steps to improve it would be great.
Thanks! Waiting for your response.

[jtpio]

Thanks @horw for cleaning this up!

Indeed the repo is a bit outdated.

[jtpio]

Thanks for working on this!

Left a couple of comments, which will hopefully help with the CI too.

[horw]

@jtpio The previous workflow was outdated as well, so I have updated it. Could you review it?

[jtpio]

Thanks @horw.

Looks like there is still an issue with the ESLint.

Wondering if the easiest would be to create a new extension from https://github.com/jupyterlab/extension-template, and simply copy the relevant existing files and config to the new extension, and push everything here?

[horw]

Thanks @horw.

Looks like there is still an issue with the ESLint.

Wondering if the easiest would be to create a new extension from https://github.com/jupyterlab/extension-template, and simply copy the relevant existing files and config to the new extension, and push everything here?

Thank you! I agree, I will try in a few days

[jtpio]

Nice, thanks!

As a heads-up, there is a draft PR in JupyterLite to simplify the current split between regular JupyterLab extensions and the JupyterLite "server" extensions (for example adding a kernel): jupyterlite/jupyterlite#1590

After this PR, adding a kernel (like the echo-kernel) will be like authoring a regular JupyterLab extension. We can keep that echo-kernel as a concrete example of https://github.com/jupyterlab/extension-template, and even consider making it a Github template if folks want to bootstrap their kernel quickly.

[horw]

@jtpio Thank you! Since you created #10, I'll close this PR.