Jupyter-lite.json not taken into account

JupyterLab
1

Hello everyone,

I’ve been playing with JupyterLite for a few weeks. I noticed a strange behavior with the use of the jupyter-lite.json file. I’ve added an extension to extend the launcher. Therefore I need to disable the original Launcher so that my custom one replace it. I’m using the following as my jupyter-lite.json:

{
    "jupyter-lite-schema-version": 0,
    "jupyter-config-data": {
      "disabledExtensions": ["@jupyterlab/launcher-extension"]
    },
    "faviconUrl": "./lab/favicon.ico"
}

When I build and then serve JupyterLite for the first time, it works fine. The Launcher is deactivated.

Now, if I delete the output or “dist” folder, build again and then serve JupyterLite, the jupyter-lite.json file is not taken into account. The Launcher isn’t deactivated. While investigating the problem I found out that if I update the json-lite.json and save it, then serving JupyterLite again would take it into account.

I was reluctant to open an issue as I’m not sure I’m doing things correctly here. But this behavior seems unexpected.

Any insights or advice on how to avoid this problem?

Thank you

2

Do you still have this problem? I cannot reproduce your issue with the recent jupyterlite.

3

Maybe you can also deleting .jupyterlite.doit.db if there is one lying around.

1 Like
4

Hi @mahendrapaipuri, yes I am still reproducing the issue. However, I tried @jtp’s recommendation and it worked. Thank you both for your responses! I appreciate it.

So, it looks like .jupyterlite.doit.db is creating this behavior. If you delete the “output” folder and don’t delete the .jupyterlite.doit.db, then the jupyter-lite.json file isn’t taken into account by the jupyter lite serve command.

1 Like
5

It’s likely related to the underlying doit caching logic in the jupyter-lite CLI.

@ThibautDR would you mind opening an issue on the JupyterLite repo? Thanks!

1 Like
6

For reference: Issue with the doit caching logic jupyter-lite CLI (Jupyter-lite.json not taken into account) · Issue #1194 · jupyterlite/jupyterlite · GitHub

1 Like
7

@ThibautDR Any updates on the above issue. I am also experincing the same issue after deleting the .jupyterlite.doit.db .