Eric Charles
Eric Charles
agree we need to look at that. As temp workaround, `--ignore-engines` could be used.
The mandatory jupyterlite deps are giving quite some headcache, especially in non webpack env like vite or next.js Having a package that covers both server kernels and browser kernels is...
> The engine "node" is incompatible with this module. Expected version ">=18.18.0
Closing as can not replicate.
Posting here work we are doing in https://github.com/datalayer/jupyter-ai-agent What is the best place to discuss: this repo, or the Zulip channels?
> AWS has a Slack workspace that allows for external connections; I can explore this if interested. I missed that sentence. TBH I would prefer having those discussions on the...
> Perhaps I'm too trusting of the AI ;) but my long term thinking here is that the AI is going to become a pretty good collaborator going forward. @Zsailer...
Just replied on https://github.com/datalayer-examples/jupyter-nextjs-example/issues/4#issuecomment-2139401440
the next-js example in this repos aims to depend on the jupyter-react source changes. If you remove the "@datalayer/jupyter-react": "workspace:^", the yarn install will pull the latest release which may...
Next-js example is now fixed in https://github.com/datalayer-examples/jupyter-nextjs-example. Closing.