Is usage of React necessary for writing JupyterLab extensions *effectively*?

I’m working through the examples: GitHub - jupyterlab/extension-examples: JupyterLab Extensions by Examples

Suddenly React Widgets came up. I don’t know React. Is it necessary to learn React in order to write client JupyterLab extensions effectively?

If React isn’t necessary for writing these extensions, I would like to just suggest that it might be a good idea to isolate the React part of the documentation, so we can learn the topics easily without having to get up to speed on React.

It is not necessary to use React in writing JupyterLab extensions. However, you can use React in JLab extensions, and the React example is for people wondering how to do that. If you don’t want to use React, don’t bother with that example.

Edit: Like it says in the instructions: " Start with the Hello World and then jump to the topic you are interested in." - if you’re not interested in using React, skip that example.

1 Like

Several of the critical learning topics have React built into them. E.g., extension-examples/basics/signals/src at master · jupyterlab/extension-examples · GitHub

I think the tutorials will be able to reach a wider audience if React were discussed separately.

Agreed - it would be nice if that example just used plain HTML buttons, and the react capabilities were confined to the react example. Can you open an issue in the example repo? Even better would be a PR.

2 Likes

Thank you. I will open the issue now and I look forward to doing the PR.

2 Likes

The PR is done: Modify Signals to render a HTML button without React. by adpatter · Pull Request #148 · jupyterlab/extension-examples · GitHub

1 Like