Eliaaazzz opened a new pull request, #38045:
URL: https://github.com/apache/beam/pull/38045

   Addresses #37977.
   
   ## Summary
   This PR migrates the Jupyter Sidepanel extension to the pip-based JupyterLab 
4
   prebuilt installation flow.
   
   ## What Changed
   - add `install.json` so JupyterLab recognizes the extension as Python-managed
   - add `style/index.js` and `styleModule` so stylesheet assets are bundled 
correctly for the prebuilt extension
   - make the prebuilt style entrypoint explicitly import the YAML panel styles 
to avoid ambiguity about whether they are included in the bundle
   - update `package.json` packaging globs so the new style entrypoint is 
included in published artifacts
   - add JupyterLab prebuilt-extension classifiers to `pyproject.toml`
   - include `src/yaml/*` in `tsconfig.json` so the YAML panel sources are 
compiled
   - update the sidepanel extension README to document the prebuilt `pip 
install` workflow and remove unnecessary legacy `jupyter lab build` steps
   - update the interactive Beam README to replace `jupyter labextension 
install @jupyter-widgets/jupyterlab-manager` with `pip install ipywidgets`
   
   ## Testing
   - `jlpm run build:lib`
   - `jlpm run build:prod`
   - `jlpm jest --runInBand`
   - `python -m pip install -e .`
   - `jupyter labextension list`
   - `python -m build --sdist --wheel`
   
   ## Context
   JupyterLab 4 favors prebuilt extensions distributed through Python packages 
instead of the legacy `labextension install/link` workflow.
   
   This change makes the sidepanel extension discoverable and installable 
through the expected Python packaging path, and aligns the docs with the 
supported installation flow.
   
   ## Checklist
   - [x] This PR addresses #37977.
   - [ ] Update `CHANGES.md` with noteworthy changes.
   - [ ] If this contribution is large, file an Apache Individual Contributor 
License Agreement.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to