Saravanan666/pypi-org huggingface dataset:
Package: jupyterlab-horizon-theme
JupyterLab Horizon ThemeVSCode Horizon Theme port for JupyterLabRequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab-horizon-themeUninstallTo remove the extension, execute:pipuninstalljupyterlab-horizon-themeContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_horizon_theme directory# Install package in development modepipinstall-e"."# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_horizon_themeIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink named@mohirio/jupyterlab-horizon-themewithin that folder.Testing the extensionFrontend testsThis extension is usingJestfor JavaScript code testing.To execute them, execute:jlpm
jlpmtestIntegration testsThis extension usesPlaywrightfor the integration tests (aka user level tests).
More precisely, the JupyterLab helperGalatais used to handle testing the extension in JupyterLab.More information are provided within theui-testsREADME.Packaging the extensionSeeRELEASECreditThanks toHorizon Theme for VSCodefor the great color scheme,
andJupyter Atom Dark Themefor CSS elements styling.
Package: jupyterlab-iframe
jupyterlab_iframeOpen a site in a widget, or add a set of "quicklinks".Installpipinstalljupyterlab_iframe
jupyterlabextensioninstalljupyterlab_iframe
jupyterserverextensionenable--pyjupyterlab_iframeOptionsExternal Sitesinstall the server extension, and add the following tojupyter_notebook_config.pyc.JupyterLabIFrame.iframes=['list','of','sites']In this example,list,of, andsiteswill be available as links in the command palette.Landing page on initial page loadc.JupyterLabIFrame.iframes=['list','of','sites']c.JupyterLabIFrame.welcome='a site to show on initial load'c.JupyterLabIFrame.local_files=['list','of','local','html','files']In this example,a sitewill open by default the first time JupyterLab is opened.Open local html file in iframec.JupyterLabIFrame.local_files=['list','of','local','html','files']Any files specified by 'local_files' will be served up as local links. By default any file on the filesystem is allowed, to disable this and only allow the list specifically designated here, setc.JupyterLabIFrame.allow_any_local = False. If you allow all, in the open dialog start the file path withlocal://.CaveatsUpdate for version v0.0.12 - Most of these are covered by#31This package uses iframes, so is subject to a few restrictions:- If Jlab is served over SSL, so must the sites (http/https must match)- If the underlying site enforces same-origin, then we cannot navigate to them (e.g. google)Similar PackagesJupyterlab-htmldisplays local html files as websites in an iframeJupyterlab-sandboxMain JLab IssueConfiguring Binder with a landing pageTo configure binder to serve a landing page, simply add the following configuration:To requirements.txt:jupyterlab_iframe>=0.2To postBuild:jupyterlabextensioninstalljupyterlab_iframe@^0.2
jupyterserverextensionenable--pyjupyterlab_iframeconfig="c.JupyterLabIFrame.welcome = 'local://binder/landing.html'"mkdir-p~/.jupyterecho-e$config>~/.jupyter/jupyter_notebook_config.py
Package: jupyterlab-image-editor
Image EditorSimple image editor in JupyterLab.This extension makes use ofmaterial design iconsreleased underApache License Version 2.0.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_image_editorUninstallTo remove the extension, execute:pipuninstalljupyterlab_image_editorContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_image_editor directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_image_editorIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedimage-editorwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-imarkdown
jupyterlab_imarkdownA JupyterLab extension to embed rich output in Markdown cells, e.g.The current value of x is {{ x }}Technical Detailsjupyterlab-imarkdownhas to do some pretty unpleasant things in order to provide interactive Markdown.
In particular, we implement our ownNotebookPanel.ContentFactoryin order to inject our ownIMarkdownCell.
This custom class implements routines to detect when the Markdown cell has been rendered, keep track of specialeval-exprDOM nodes,
and update these DOM nodes with the result of kernel execution.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_imarkdownUninstallTo remove the extension, execute:pipuninstalljupyterlab_imarkdownContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_imarkdown directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when needed`jlpmrunwatch`# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_imarkdownIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab-imarkdownwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-indent-guides
jupyterlab-indent-guidesIndentation guides for JupyterLabRequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab-indent-guidesUninstallTo remove the extension, execute:pipuninstalljupyterlab-indent-guidesSettingsSettings for the extension can be customized in theNotebookpage of the Settings Editor, below theThemesetting.ContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab-indent-guides directory# Install package in development modepipinstall-e"."# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab-indent-guidesIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab-indent-guideswithin that folder.Testing the extensionFrontend testsThis extension is usingJestfor JavaScript code testing.To execute them, execute:jlpm
jlpmtestIntegration testsThis extension usesPlaywrightfor the integration tests (aka user level tests).
More precisely, the JupyterLab helperGalatais used to handle testing the extension in JupyterLab.More information are provided within theui-testsREADME.Packaging the extensionSeeRELEASE
Package: jupyterlab-interactive-dashboard-editor
jupyterlab-interactive-dashboard-editorInteractively create and customize dashboards in JupyterLabAdditional GifsClick to expandAdd and rearrange outputs on dashboards right from your notebook.Add outputs from multiple notebooks.See changes immediately.Preview your dashboard and interact with widgets in present mode.Undo and redo.Add markdown too.Save dashboards to file,Load them up,And edit them again!RequirementsJupyterLab >= 2.0InstallFor JupyterLab 3+:pipinstalljupyterlab-interactive-dashboard-editorFor JupyterLab 2.x:jupyterlabextensioninstalljupyterlab-interactive-dashboard-editor
jupyterlabbuildNote: You will need NodeJS to install the extension for JupterLab 2.x.ContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab-interactive-dashboard-editor directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseUninstallFor JupyterLab 3+:pipuninstall-interactive-dashboard-editorFor JupyterLab 2.x:jupyterlabextensionuninstalljupyterlab-interactive-dashboard-editor
Package: jupyterlab-itables
A Jupyter Lab extension for itablesThis extension exposes thejqueryanddatatables.netlibraries and css as static files in Jupyter Lab.The purpose of doing this is to allow theitablespackage to have anoffline modein Jupyter Lab.Install it in the Python environment you use to launch Jupyter Lab with:pipinstalljupyterlab-itablesThen relaunch Jupyter Lab withjupyterlabAssuming that Jupyter Lab is running on port 8888, you will be able to access the static files at e.g.http://localhost:8888/static/itables/jquery/dist/jquery.min.jshttp://localhost:8888/static/itables/datatables.net-dt/css/jquery.dataTables.min.csshttp://localhost:8888/static/itables/datatables.net/js/jquery.dataTables.mjsHow to develop this extensionAssuming that you have conda and mamba,
you can create a minimal Jupyter Lab environment withmambaenvcreate--fileenvironment.ymlor update it withmambaenvupdate--fileenvironment.ymlActivate that environment withcondaactivatejupyterlab-itables-devThen build the extension in development mode withpipinstall-ve.In development mode the extension needs to be enabled manually with:jupyterserverextensionenable--pyjupyterlab_itablesHow to release a new version manuallyClean the project files withrm-rfnode_modulesjupyterlab_itables/staticdistbuildpackage-lock.jsonUpgrade the version number insetup.py, then:pythonsetup.pysdistbdist_wheelCheck the size and the contents of the.tar.gzfile in thedistfolder,
and then upload it topypiwithtwineuploaddist/jupyterlab-itables-xxx.tar.gz
Package: jupyterlab-jherng
jupyterlab-jherngA JupyterLab theme for me.RequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab-jherngUninstallTo remove the extension, execute:pipuninstalljupyterlab-jherngContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab-jherng directory# Install package in development modepipinstall-e"."# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab-jherngIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink named@jherng/jupyterlab-jherngwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-jitsi
jupyterlab-jitsiA jupyterlab extension to add a Jitsi chatThis extension is composed of a Python package namedjupyterlab-jitsifor the server extension and a NPM package namedjupyterlab-jitsifor the frontend extension.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab-jitsiUninstallTo remove the extension, execute:pipuninstalljupyterlab-jitsiTroubleshootIf you are seeing the frontend extension, but it is not working, check
that the server extension is enabled:jupyterserverextensionlistIf the server extension is installed and enabled, but you are not seeing
the frontend extension, check the frontend extension is installed:jupyterlabextensionlistContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab-jitsi directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Server extension must be manually installed in develop modejupyterserverextensionenablejupyterlab-jitsi# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstall# Server extension must be manually disabled in develop modejupyterserverextensiondisablejupyterlab-jitsi
pipuninstalljupyterlab-jitsiIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab-jitsiwithin that folder.
Package: jupyterlab-js-logs
jupyterlab-js-logsJupyterLab extension to show the js logs from the browser dev tools consoleRequirementsJupyterLab >= 2.0Installjupyterlabextensioninstalljupyterlab-js-logsContributingThis extension was bootstrapped from thecustom-log-consoleexample contributed byCarlos Herrero, from thejupyterlab-extension-examplesrepository.InstallThejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Move to jupyterlab-js-logs directory# Install dependenciesjlpm# Build Typescript sourcejlpmbuild# Link your development version of the extension with JupyterLabjupyterlabextensioninstall.# Rebuild Typescript source after making changesjlpmbuild# Rebuild JupyterLab after making any changesjupyterlabbuildYou can watch the source directory and run JupyterLab in watch mode to watch for changes in the extension's source and automatically rebuild the extension and application.# Watch the source directory in another terminal tabjlpmwatch# Run jupyterlab in watch mode in one terminal tabjupyterlab--watchNow every change will be built locally and bundled into JupyterLab. Be sure to refresh your browser page after saving file changes to reload the extension (note: you'll need to wait for webpack to finish, which can take 10s+ at times).Uninstalljupyterlabextensionuninstalljupyterlab-js-logs
Package: jupyterlab-k8s-explorer
jupyterlab_k8s_explorerA JupyterLab extension for exploring and managing k8s resourcesRequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_k8s_explorerUninstallTo remove the extension, execute:pipuninstalljupyterlab_k8s_explorerContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_k8s_explorer directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_k8s_explorerIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab_k8s_explorerwithin that folder.Testing the extensionFrontend testsThis extension is usingJestfor JavaScript code testing.To execute them, execute:jlpm
jlpmtestIntegration testsThis extension usesPlaywrightfor the integration tests (aka user level tests).
More precisely, the JupyterLab helperGalatais used to handle testing the extension in JupyterLab.More information are provided within theui-testsREADME.Packaging the extensionSeeRELEASE