all xeus kernels fail with the same error as https://github.com/jupyterlite/xeus-sqlite-kernel/issues/10.

Interestingly I can locally install all of them via pip and they work without that issue

The current demo is hardwired to use a specific (fixed) all.json config file which itemises the files to be displayed in the file directory listing.

To make this repo more useful as a possible template repo, from which folk can deploy their own notebook seeded demo site, a new all.json file should be created that captures the files to be listed.

There is a fragment of Python code in JupyterLite conf.py that could be split out into a simple CLI command to achieve this: https://github.com/jtpio/jupyterlite/blob/695373748db6c5aa015224e94d4aa8679eb34ef2/docs/conf.py#L142

To make things conventional / easier to identify which files to copy over, it might be worth having something like a content directory into which the notebook files, image files, maybe python files etc etc intended for distribution are placed.

At the moment the Github Action only copies over *.csv and *.ipynb files: https://github.com/jtpio/jupyterlite-demo/blob/98eb9db9c3cd68e10caa0e265d9be38db9ecb30d/.github/workflows/deploy.yml#L28

Description

I believe ipywidgets fail to install in the Jupyterlite deployment of the jupyterlite/demo repo. It was working in late July.

This started as a discussion here: https://discourse.jupyter.org/t/miscellaneous-questions-on-the-usage-of-jupyterlite

Reproduce

1. Open a fresh Jupyterlite demo from https://jupyterlite.github.io/demo/lab/
2. Create and run cell with

import piplite
await piplite.install(['ipywidgets'])

3. It yields a ValueError: Can't find a pure Python 3 wheel for 'widgetsnbextension~=4.0'.

Expected behavior

ipywidgets should install fine. This is the case in the official Jupyterlite demo https://jupyterlite.readthedocs.io/en/latest/_static/lab/, so there must be some divergence between the two deployments.

Context

• JupyterLite version: Version 0.1.0-beta.12
• Operating System and version: Ubuntu 22.04
• Browser and version: Firefox 104 (as a snap from Ubuntu)

It took me some digging to understand a few key things I needed for a Jupyterlite "Quickstart," where my use case was basically "put some notebooks on GitHub Pages, or other static site hosting, and have them be shareable and interactive (thanks to Jupyterlite)."

The minimal quickstart steps seem to be:

mkdir content && cp <some notebook>.ipynb content/
pip install jupyterlite jupyterlab
jupyter lite build --contents content --output-dir dist

At that point, dist/ is a static bundle that can be dropped anywhere, copied into an existing GitHub Pages site dir, etc.

The jupyterlab dependency was tricky to figure out. It's required for example notebooks to show up on the frontend. Otherwise, jupyter lite build --contents content will ≈silently fail to output api/contents/all.json (which is required for example notebooks from content/ to be presented to users, cf. https://github.com/jupyterlite/jupyterlite/issues/318#issuecomment-945492049).

Some other thoughts:

• deploy.yml in this repo is a good template for auto-publishing via GHA, which I know is somewhat described in this README, but took me a while to find+appreciate.
• Forking this repo to get an auto-published GitHub Pages site, with notebooks from contents/, is a powerful "Quickstart" that I didn't glean from my initial skim of relevant repos/docs.
• A lot of this info (like the existence and structure of this demo repo) could be called out more prominently in the main jupyterlite docs (and perhaps in an example notebook in this repo / the public demo site?). Something like how-to-host-your-own-jupyterlite.ipynb, easily findable in the main demo.

Anyway, I appreciate that the README.md in this repo is geared toward beginners; perhaps some of the above (and the README.md I wrote in this PR / my fork) could go in a quickstart.md or something?

Thoughts welcome, I'm not actually proposing to replace the README wholesale, this is just my take on explaining a quickstart to someone who's already more proficient with Git{,Hub}.

Problem

To make it event clearier and show how to use the GitHub template.

Suggested Improvement

There is already a screenshot in https://github.com/jupyterlite/demo#usage.

@martinRenou maybe we could update it and use the screencast from this tweet? https://twitter.com/martinRenou/status/1415683682036162567

Hi,

I try to configure the look and feel of the resulting embedded notebook. My (first) goal is to change the rendering layout to 'side-by-side'. Could you please explain me how to do that ? I tried several things (overrides.json, jupyter-lite.json in different folder, etc) but with no luck. I guess the closest thing I did is to add a jupyter-lite.json file in the root directory of my repo with the following content: `{

"jupyter-lite-schema-version": 0,
"jupyter-config-data": {
  "disabledExtensions": [
    "@jupyterlab/drawio-extension",
    "jupyterlab-kernel-spy",
    "jupyterlab-tour"
  ]
},
"settingsOverrides": {
     "@jupyterlab/notebook-extension:tracker": {
        "renderingLayout": "side-by-side"
     },
    "@jupyterlab/apputils-extension:palette": {"modal": false}
 }

}`

the file seems considered since the disabled extensions are actually disabled but the rendering layout is not changed :-/ the repo is here: https://github.com/jdeantoni/iiwjupylite and the resulting page here: https://jdeantoni.github.io/iiwjupylite/lab/index.html

any help would be appreciated thanks

Problem

There is no section about collaboration specific to the demo. In the jupyterlite docs, it says that it should be enabled but I can't see this on my instance which is a vanilla fork of the demo.

I also tried to deploy my own from scratch, and the collaboration works on my machine but not when it is deployed on e.g. github pages nor gitlab pages.

I have tried to append room=0, put a specific room number in the configuration that I then put in the url, but the two open windows don't show the other modifications.

Suggested Improvement

A section that says how to make real-time collaboration work

Problem

In the template section the links to Actions and Settings etc dont lead to the approriate repo tabs, rather to parts of the code that are then non-existent.

so here:

the actions link leads to the non-existent https://github.com/jupyterlite/demo/blob/main/actions

Suggested Improvement

Make these links lead to the approriate https://github.com/jupyterlite/demo/actions

Fixes https://github.com/jupyterlite/xeus-lua-kernel/issues/24

Now that jupyterlite-xeus-lua is published to PyPI: https://pypi.org/project/jupyterlite-xeus-lua/

cc @DerThorsten

It looks like the only thing needed to make that repo automatically deployable on Netlify (for folks generating theirs with the template) is to add a runtime.txt file with the following content:

3.7

To make sure to be using Python 3.7.

And then specify the build command in the "Deploy Settings":

jupyter lite build --output-dir dist --debug

The demo notebook is misleading - when I tried running the demo locally at least, there is a lot of whitespace at the top of the notebook that makes it look like the page is blank (and broken....)

Are the line breaks in the notebook for a reason?

Problem

I would like it if we could use dotnet core kernel then display the content in html using ObservableHQ []

Use cases:

-dotnet-CLR -repl

• taking advantage of dotnet DLR ,foreign code interop and CIL bytecode.
• utilizing onnx interference runtime and deployment in most platform natively with enhanced performance .
• cross platform native deamon/services communication protocol to bridge plugins with native messaging in client apps --automation with powershell?
• interactive programming/learning += desktop editors in mobile through web RWD+PWA . --blazor in notebook?
• interactive data plotting and visualization displayed in html with widget and web component .
• [Multi-language notebooks&variable sharing] within the same notebook

Proposed Solution

Add an option to switch computing kernel so we cloud use dotnet libraries usage example

Additional context

https://nteract.io/kernels/dotnet https://github.com/nteract/nteract/tree/master/applications/jupyter-extension

Description

I used your document to run a local instance of jupyterlite on port 8000 but stocks on [*], i also run your online and had the same problem. I should note that, the javascript kernel is working okay

Paste the output from your browser Javascript console here.

The JupyterLite demo currently shows how to add custom content to the site, as well as additional app config settings.

It would be useful for a documented demo of how to add a custom extension, eg from a pre-built wheel.

Problem

For now we manually update this repo to bump the version of jupyterlite when there is a new release. For example: https://github.com/jupyterlite/demo/pull/43

It would be great if this could be automated instead.

Proposed Solution

Probably just parsing and writing to requirements.txt should be enough for now.

Additional context

JupyterLab Desktop has a workflow to do that with JupyterLab releases: https://github.com/jupyterlab/jupyterlab-desktop/blob/master/.github/workflows/sync_lab_release.yml

Problem

Many potential users of jupyterlite are likely to consider themselves "notebook users" rather than developers. This template repo helps provide an on-ramp to unexperienced users with a way to get started with their own deployment of jupyterlite, as well as exploring what's possible via the demo notebooks.

Such users might be consider themselves "notebook users" rather than developers and might be frustrated if things they expect to work don't (yet) work.

It might be useful to have a notebook of "not yet working" examples of things that folk are likely to try but that don't yet work, with workarounds if available, perhaps with a brief explanation of why they don't (yet) work.

See also: https://github.com/jupyterlite/jupyterlite/issues/199

Suggested Improvement

Create a notebook with a set of "not yet working" items.

For example:

• %pip not available [related issue]
• pd.read_csv() file not found; sqliite file not found etc. [related issue]
• shell commands and line magics that make use of shell commands won't work

If a user has visited the site from a particular browser and then revisits the demo site at a later time, perhaps noticing from the repo that additional demo examples have been added, or original examples have been updated, how will their browser respond?

• will new files be added to browser storage (which already has state associated with the demo URL)?
• will updated files overwrite similarly named files in browser storage?

How could a user "update" their local state to reflect the current repo live demo state? (I guess one way might be to run the browser as a new private browser session, but how many folk would think to do that?)