JupyterLab Spreadsheet: A Simple Spreadsheet Viewer into JupyterLab.

JupyterLab Spreadsheet

Image depicting the plugin displaying a simple XLS workbook

This plugin adds a simple spreadsheet viewer to JupyterLab.

jupyterlab-spreadsheet supports XLS, XLSX, ODS, and CSV files, and allows for basic formatting (such as cell merges). The plugin is in alpha, and doesn't support all features of workbooks (advanced formatting, formulas, etc.).

Refer to the changelog for detailed release notes.

Getting Started

Installing jupyterlab-spreadsheet is easy. Just run the following command:

jupyter labextension install jupyterlab-spreadsheet

If you already have JupyterLab running, you just have to refresh the page.

To open a workbook, navigate to it in the file viewer and double-click on it. To open CSV files in the plugin, right click on the file and use "Open With > Spreadsheet".

Contributing

Contributions are always welcome! jupyterlab-spreadsheet is built off of the 6pac fork of SlickGrid, and uses SheetJS to parse workbooks.

When filing issues, please be sure to give reproduction steps and any relevant error messages or console output. This helps me track down the cause and get a fix out sooner.

Building from Source

To build from sources, clone this repository into a convenient directory and cd into it from a terminal. Then, run the following commands:

yarn install
yarn build
jupyter labextension install .

Then, start JupyterLab as you would normally. File watchers are available via yarn build --watch and jupyter lab --watch.


Author: quigleyj97
Source Code: https://github.com/quigleyj97/jupyterlab-spreadsheet
License: BSD-3-Clause License

#jupyterlab #jupyter #typescript 

What is GEEK

Buddha Community

JupyterLab Spreadsheet: A Simple Spreadsheet Viewer into JupyterLab.

JupyterLab Spreadsheet: A Simple Spreadsheet Viewer into JupyterLab.

JupyterLab Spreadsheet

Image depicting the plugin displaying a simple XLS workbook

This plugin adds a simple spreadsheet viewer to JupyterLab.

jupyterlab-spreadsheet supports XLS, XLSX, ODS, and CSV files, and allows for basic formatting (such as cell merges). The plugin is in alpha, and doesn't support all features of workbooks (advanced formatting, formulas, etc.).

Refer to the changelog for detailed release notes.

Getting Started

Installing jupyterlab-spreadsheet is easy. Just run the following command:

jupyter labextension install jupyterlab-spreadsheet

If you already have JupyterLab running, you just have to refresh the page.

To open a workbook, navigate to it in the file viewer and double-click on it. To open CSV files in the plugin, right click on the file and use "Open With > Spreadsheet".

Contributing

Contributions are always welcome! jupyterlab-spreadsheet is built off of the 6pac fork of SlickGrid, and uses SheetJS to parse workbooks.

When filing issues, please be sure to give reproduction steps and any relevant error messages or console output. This helps me track down the cause and get a fix out sooner.

Building from Source

To build from sources, clone this repository into a convenient directory and cd into it from a terminal. Then, run the following commands:

yarn install
yarn build
jupyter labextension install .

Then, start JupyterLab as you would normally. File watchers are available via yarn build --watch and jupyter lab --watch.


Author: quigleyj97
Source Code: https://github.com/quigleyj97/jupyterlab-spreadsheet
License: BSD-3-Clause License

#jupyterlab #jupyter #typescript 

Oriana Zabell

Oriana Zabell

1626423027

How To Resolve Unable To Locate PDF Viewer Error?

There are certain important Windows components and applications that are required to print any document. However, if you come across any issue while printing your payroll tax forms and statements, then it is because of damage in the windows print components or improper setup of the QuickBooks Desktop application. In such situations, you might end up unable to locate the PDF viewer error. However, one needs profound knowledge of Windows print components like Adobe and XPS Viewer to fix this issue. Moreover, you can follow the troubleshooting solutions mentioned in this blog to fix

What Triggers QuickBooks Can’t Connect PDF Viewer Error?****

Below we have listed some of the common reasons that can result in unable to locate the PDF viewer error:

  • You must have installed an outdated version of Adobe Reader on Windows.
  • Adobe Reader is not set up as the default PDF viewer application in QuickBooks Desktop.
  • You haven’t installed the latest QuickBooks Desktop updates.
  • Qbprint.qbp file is damaged or missing from the installation directory.

**

Troubleshooting Solutions To Fix PDF Viewer Not Working Error **

Here, we have listed some of the effective resolution methods by implementing which you would be able to resolve Unable to Locate PDF Viewer issue:

Step 1: Repair, Update and Reinstall Adobe Reader

Update Adobe Reader

  • Firstly, you have to open the Adobe Acrobat Reader Download Page by clicking here.
  • Make sure to note down the version displayed on the page and open the Adobe Reader app on Windows.
  • Go to the Help menu and select About Adobe Reader.
  • Now, you have to match the product version displayed on the page and check if it is the same as shown on Adobe’s website.
  • If the product version does not match, then go to the Help menu once again and select the Check for Updates option.
  • At last, update the PDF Viewer by following the instructions that appear on your screen.

Repair Adobe Acrobat Reader

  • Close all the applications that are running in the background on the Windows.
  • Open Adobe Acrobat Reader and go to the Help menu.
  • From there, click on the Repair Acrobat Installation option.
  • Wait until the application repairs itself and once the repair-completed message appears on your screen, restart your computer and try to print a document once again using QuickBooks.

Reinstall Adobe PDF Viewer

  • Open the Run dialog box by pressing Windows + R keys simultaneously.
  • Then, type appwiz.cpl in the text space and click OK.
  • Now, go to the Programs and Features window and click on View Installed Updates.
  • Right-click Adobe and select Uninstall.
  • Open your internet browser and go to the Adobe Acrobat Reader download page.
  • Click the Install Now option and select the correct Windows version from the drop-down list.
  • Once the update file is downloaded, click on Run.
  • Once installed, click on Finish and check if Unable to Locate PDF Viewer error persists or not.

Step 2: Rename Qbprint.qbp File

  • Open Windows File Manager and click on the Organize option from the top left corner.
  • Then, select the Folder and Search option from the drop-down menu.
  • Now, go to the View tab and unmark the Show Hidden Files, Folders, or Drives checkbox.
  • Go to the Program Data folder in the C Drive and open the Intuit Folder.
  • Double-click the QuickBooks folder and right-click Qbprint.qbp file.
  • After that, click on the rename option and type Qbprint.old.
  • Make sure to save the file name and check whether the Unable to Locate PDF Viewer error persists or not.

Summing It Up

We hope the steps mentioned in this blog would have helped you fix Unable to Locate PDF Viewer Error without any hassle. However, if you get stuck and need any further assistance, we would suggest you to get in touch with our experts by giving us a call on our Asquare Cloud Hosting Helpline Number (855)-948-3651.

#pdf reader not found error, #pdf viewer not working error, #quickbooks can’t connect pdf viewer, #can’t open pdf viewer in quickbooks, #enable pdf viewer in quickbooks,

Jupyterlab: JupyterLab Computational Environment.

JupyterLab

An extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture.

JupyterLab is the next-generation user interface for Project Jupyter offering all the familiar building blocks of the classic Jupyter Notebook (notebook, terminal, text editor, file browser, rich outputs, etc.) in a flexible and powerful user interface.

JupyterLab can be extended using npm packages that use our public APIs. The prebuilt extensions can be distributed via PyPI, conda, and other package managers. The source extensions can be installed directly from npm (search for jupyterlab-extension) but require an additional build step. You can also find JupyterLab extensions exploring GitHub topic jupyterlab-extension. To learn more about extensions, see the user documentation.

Read the current JupyterLab documentation on ReadTheDocs.


Getting started

Installation

If you use conda, mamba, or pip, you can install JupyterLab with one of the following commands.

  • If you use conda:
conda install -c conda-forge jupyterlab
  • If you use mamba:
mamba install -c conda-forge jupyterlab
  • If you use pip:
pip install jupyterlab
  • If installing using pip install --user, you must add the user-level bin directory to your PATH environment variable in order to launch jupyter lab. If you are using a Unix derivative (e.g., FreeBSD, GNU/Linux, macOS), you can do this by running export PATH="$HOME/.local/bin:$PATH". If you are using a macOS version that comes with Python 2, run pip3 instead of pip.

For more detailed instructions, consult the installation guide. Project installation instructions from the git sources are available in the contributor documentation.

Installing with Previous Versions of Jupyter Notebook

When using a version of Jupyter Notebook earlier than 5.3, the following command must be run after installing JupyterLab to enable the JupyterLab server extension:

jupyter serverextension enable --py jupyterlab --sys-prefix

Running

Start up JupyterLab using:

jupyter lab

JupyterLab will open automatically in the browser. See the documentation for additional details.

If you encounter an error like "Command 'jupyter' not found", please make sure PATH environment variable is set correctly. Alternatively, you can start up JupyterLab using ~/.local/bin/jupyter lab without changing the PATH environment variable.

Prerequisites and Supported Browsers

The latest versions of the following browsers are currently known to work:

  • Firefox
  • Chrome
  • Safari

See our documentation for additional details.


Getting help

We encourage you to ask questions on the Discourse forum. A question answered there can become a useful resource for others.

Bug report

To report a bug please read the guidelines and then open a Github issue. To keep resolved issues self-contained, the lock bot will lock closed issues as resolved after a period of inactivity. If a related discussion is still needed after an issue is locked, please open a new issue and reference the old issue.

Feature request

We also welcome suggestions for new features as they help make the project more useful for everyone. To request a feature please use the feature request template.


Development

Extending JupyterLab

To start developing an extension for JupyterLab, see the developer documentation and the API docs.

Contributing

To contribute code or documentation to JupyterLab itself, please read the contributor documentation.

JupyterLab follows the Jupyter Community Guides.

License

JupyterLab uses a shared copyright model that enables all contributors to maintain the copyright on their contributions. All code is licensed under the terms of the revised BSD license.

Team

JupyterLab is part of Project Jupyter and is developed by an open community. The maintenance team is assisted by a much larger group of contributors to JupyterLab and Project Jupyter as a whole.

JupyterLab's current maintainers are listed in alphabetical order, with affiliation, and main areas of contribution:

  • Mehmet Bektas, Netflix (general development, extensions).
  • Alex Bozarth, IBM (general development, extensions).
  • Eric Charles, Datalayer, (general development, extensions).
  • Frédéric Collonval, QuantStack (general development, extensions).
  • Martha Cryan, IBM (general development, extensions).
  • Afshin Darian, Two Sigma (co-creator, application/high-level architecture, prolific contributions throughout the code base).
  • Vidar T. Fauske, JPMorgan Chase (general development, extensions).
  • Brian Granger, AWS (co-creator, strategy, vision, management, UI/UX design, architecture).
  • Jason Grout, Databricks (co-creator, vision, general development).
  • Michał Krassowski, University of Oxford (general development, extensions).
  • Max Klein, JPMorgan Chase (UI Package, build system, general development, extensions).
  • Gonzalo Peña-Castellanos, QuanSight (general development, i18n, extensions).
  • Fernando Perez, UC Berkeley (co-creator, vision).
  • Isabela Presedo-Floyd, QuanSight Labs (design/UX).
  • Steven Silvester, MongoDB (co-creator, release management, packaging, prolific contributions throughout the code base).
  • Jeremy Tuloup, QuantStack (general development, extensions).

Maintainer emeritus:

  • Chris Colbert, Project Jupyter (co-creator, application/low-level architecture, technical leadership, vision, PhosphorJS)
  • Jessica Forde, Project Jupyter (demo, documentation)
  • Tim George, Cal Poly (UI/UX design, strategy, management, user needs analysis).
  • Cameron Oelsen, Cal Poly (UI/UX design).
  • Ian Rose, Quansight/City of LA (general core development, extensions).
  • Andrew Schlaepfer, Bloomberg (general development, extensions).
  • Saul Shanabrook, Quansight (general development, extensions)

This list is provided to give the reader context on who we are and how our team functions. To be listed, please submit a pull request with your information.


Weekly Dev Meeting

We have videoconference meetings every week where we discuss what we have been working on and get feedback from one another.

Anyone is welcome to attend, if they would like to discuss a topic or just listen in.

Notes are archived on GitHub JupyterLab team compass.

Download Details:

Author: jupyterlab
Source Code: https://github.com/jupyterlab/jupyterlab 
License: View license

#jupyterlab #jupyter 

Grace  Lesch

Grace Lesch

1652025600

JupyterLab GitHub: GitHub Integration For JupyterLab

JupyterLab GitHub

A JupyterLab extension for accessing GitHub repositories.

What this extension is

When you install this extension, an additional filebrowser tab will be added to the left area of JupyterLab. This filebrowser allows you to select GitHub organizations and users, browse their repositories, and open the files in those repositories. If those files are notebooks, you can run them just as you would any other notebook. You can also attach a kernel to text files and run those. Basically, you should be able to open any file in a repository that JupyterLab can handle.

Here is a screenshot of the plugin opening this very file on GitHub: gitception

What this extension is not

This is not an extension that provides full GitHub access, such as saving files, making commits, forking repositories, etc. For it to be so, it would need to more-or-less reinvent the GitHub website, which represents a huge increase in complexity for the extension.

A note on rate-limiting

This extension has both a client-side component (that is, JavaScript that is bundled with JupyterLab), and a server-side component (that is, Python code that is added to the Jupyter server). This extension will work with out the server extension, with a major caveat: when making unauthenticated requests to GitHub (as we must do to get repository data), GitHub imposes fairly strict rate-limits on how many requests we can make. As such, you are likely to hit that limit within a few minutes of work. You will then have to wait up to an hour to regain access.

For that reason, we recommend that you take the time and effort to set up the server extension as well as the lab extension, which will allow you to access higher rate-limits. This process is described in the installation section.

Prerequisites

  • JupyterLab 3.0
  • A GitHub account for the server extension

Installation

As discussed above, this extension has both a server extension and a lab extension. Both extensions will be installed by default when installing from PyPI, but you may have only lab extension installed if you used the Extension Manager in JupyterLab 3.x.

We recommend completing the steps described below as to not be rate-limited. The purpose of the server extension is to add GitHub credentials that you will need to acquire from https://github.com/settings/developers, and then to proxy your request to GitHub.

For JupyterLab version older than 3 please see the instructions on the 2.x branch.

1. Installing both server and prebuilt lab extension

To install the both the server extension and (prebuilt) lab extension, enter the following in your terminal:

pip install jupyterlab-github

After restarting JupyterLab, the extension should work, and you can experience the joys of being rate-limited first-hand!

2. Getting your credentials from GitHub

There are two approaches to getting credentials from GitHub: (1) you can get an access token, (2) you can register an OAuth app. The second approach is not recommended, and will be removed in a future release.

Getting an access token (recommended)

You can get an access token by following these steps:

  1. Verify your email address with GitHub.
  2. Go to your account settings on GitHub and select "Developer Settings" from the left panel.
  3. On the left, select "Personal access tokens"
  4. Click the "Generate new token" button, and enter your password.
  5. Give the token a description, and check the "repo" scope box.
  6. Click "Generate token"
  7. You should be given a string which will be your access token.

Remember that this token is effectively a password for your GitHub account. Do not share it online or check the token into version control, as people can use it to access all of your data on GitHub.

Setting up an OAuth application (deprecated)

This approach to authenticating with GitHub is deprecated, and will be removed in a future release. New users should use the access token approach. You can register an OAuth application with GitHub by following these steps:

  1. Log into your GitHub account.
  2. Go to https://github.com/settings/developers and select the "OAuth Apps" tab on the left.
  3. Click the "New OAuth App" button.
  4. Fill out a name, homepage URL, description, and callback URL in the form. This extension does not actually use OAuth, so these values actually do not matter much, you just need to enter them to register the application.
  5. Click the "Register application" button.
  6. You should be taken to a new page with the new application information. If you see fields showing "Client ID" and "Client Secret", congratulations! These are the strings we need, and you have successfuly set up the application.

It is important to note that the "Client Secret" string is, as the name suggests, a secret. Do not share this value online, as people may be able to use it to impersonate you on GitHub.

3. Enabling and configuring the server extension

The server extension will be enabled by default on new JupyterLab installations if you installed it with pip. If you used Extension Manager in JupyterLab 3.x, please uninstall the extension and install it again with the instructions from point (1).

Confirm that the server extension is installed and enabled with:

jupyter server extension list

you should see the following:

- Validating jupyterlab_github...
     jupyterlab_github 3.0.0 OK

On some older installations (e.g. old JupyterHub versions) which use jupyter notebook server instead of the new jupyter-server, the extension needs to show up on the legacy serverextensions list (note: no space between server and extension):

jupyter serverextension list

If the extension is not enabled run:

jupyter server extension enable jupyterlab_github

or if using the legacy notebook server:

jupyter serverextension enable jupyterlab_github

You now need to add the credentials you got from GitHub to your server configuration file. Instructions for generating a configuration file can be found here. Once you have identified this file, add the following lines to it:

c.GitHubConfig.access_token = '< YOUR_ACCESS_TOKEN >'

where "< YOUR_ACCESS_TOKEN >" is the string value you obtained above. If you generated an OAuth app, instead enter the following:

c.GitHubConfig.client_id = '< YOUR_CLIENT_ID >'
c.GitHubConfig.client_secret = '< YOUR_CLIENT_SECRET >'

where "< YOUR_CLIENT_ID >" and "< YOUR_CLIENT_SECRET >" are the app values you obtained above.

With this, you should be done! Launch JupyterLab and look for the GitHub tab on the left!

Customization

You can set the plugin to start showing a particular repository at launch time. Open the "Advanced Settings" editor in the Settings menu, and under the GitHub settings add

{
  "defaultRepo": "owner/repository"
}

where owner is the GitHub user/org, and repository is the name of the repository you want to open.


Author: jupyterlab
Source Code: https://github.com/jupyterlab/jupyterlab-github
License: BSD-3-Clause license

#jupyterlab #jupyter #github 

Grace  Lesch

Grace Lesch

1651960800

Jupyterlab Git: A Git Extension For JupyterLab

jupyterlab-git

A JupyterLab extension for version control using Git

ui_glow_up

To see the extension in action, open the example notebook included in the Binder demo.

Requirements

  • JupyterLab >= 3.0 (older version available for 2.x)
  • Git (version >=2.x)

Usage

Install

To install perform the following steps, with pip:

pip install --upgrade jupyterlab jupyterlab-git

or with conda:

conda install -c conda-forge jupyterlab jupyterlab-git

For JupyterLab < 3, you will need to run the following command after installing the package:

jupyter lab build

Uninstall

pip uninstall jupyterlab-git

or with conda:

conda remove jupyterlab-git

For JupyterLab < 3, you will also need to run the following command after removing the Python package:

jupyter labextension uninstall @jupyterlab/git

Settings

Authentication to remote repository hosts

If you are seeing errors similar to [E yyyy-mm-dd hh:mm:ss ServerApp] 500 POST /git/<clone|push|pull|status> on the console which is running the JupyterLab server, you probably need to set up a credentials store for your local Git repository.

This extension tries to handle credentials for HTTP(S) connections (if you don't have set up a credential manager). But not for other SSH connections.

For Windows users, it is recommended to install git for windows. It will automatically set up a credential manager. In order to connect to a remote host, it is recommended to use SSH.

HTTP(S) protocol

The extension can cache temporarily (by default for an hour) credentials. To use the caching, you will need to check the option Save my login temporarily in the dialog asking your credentials.

You can set a longer cache timeout; see Server Settings.

This is a new feature since v0.37.0

SSH protocol

Here are the steps to follow to set up SSH authentication (skip any that is already accomplished for your project):

  1. Create a SSH key
  2. Register the public part of it to your Git server:
  3. Optionally, if you have more than one key managed by your ssh agent: Create a config file for the ssh-agent
  4. Tell your local Git repository to connect to remote via ssh

You should now be able to pull and push committed changes to and from your remote repository using the respective buttons on the top of the extension's panel.

UI Settings

Once installed, extension behavior can be modified via the following settings which can be set in JupyterLab's advanced settings editor:

  • blockWhileCommandExecutes: suspend JupyterLab user interaction until Git commands (e.g., commit, pull, reset, revert) finish executing. Setting this to true helps mitigate potential race conditions leading to data loss, conflicts, and a broken Git history. Unless running a slow network, UI suspension should not interfere with standard workflows. Setting this to false allows for actions to trigger multiple concurrent Git actions.
  • cancelPullMergeConflict: cancel pulling changes from a remote repository if there exists a merge conflict. If set to true, when fetching and integrating changes from a remote repository, a conflicting merge is canceled and the working tree left untouched.
  • commitAndPush: Whether to trigger or not a push for each commit; default is false.
  • disableBranchWithChanges: disable all branch operations, such as creating a new branch or switching to a different branch, when there are changed/staged files. When set to true, this setting guards against overwriting and/or losing uncommitted changes.
  • displayStatus: display Git extension status updates in the JupyterLab status bar. If true, the extension displays status updates in the JupyterLab status bar, such as when pulling and pushing changes, switching branches, and polling for changes. Depending on the level of extension activity, some users may find the status updates distracting. In which case, setting this to false should reduce visual noise.
  • doubleClickDiff: double click a file in the Git extension panel to open a diff of the file instead of opening the file for editing.
  • historyCount: number of commits shown in the history log, beginning with the most recent. Displaying a larger number of commits can lead to performance degradation, so use caution when modifying this setting.
  • refreshIfHidden: whether to refresh even if the Git tab is hidden; default to false (i.e. refresh is turned off if the Git tab is hidden).
  • refreshInterval: number of milliseconds between polling the file system for changes. In order to ensure that the UI correctly displays the current repository status, the extension must poll the file system for changes. Longer polling times increase the likelihood that the UI does not reflect the current status; however, longer polling times also incur less performance overhead.
  • simpleStaging: enable a simplified concept of staging. When this setting is true, all files with changes are automatically staged. When we develop in JupyterLab, we often only care about what files have changed (in the broadest sense) and don't need to distinguish between "tracked" and "untracked" files. Accordingly, this setting allows us to simplify the visual presentation of changes, which is especially useful for those less acquainted with Git.

Server Settings

  • JupyterLabGit.actions.post_init: Set post git init actions. It is possible to provide a list of commands to be executed in a folder after it is initialized as Git repository.
  • JupyterLabGit.credential_helper: Git credential helper to set to cache the credentials. The default value is cache --timeout=3600 to cache the credentials for an hour. If you want to cache them for 10 hours, set cache --timeout=36000.

How to set server settings?

In $HOME/.jupyter/jupyter_notebook_config.py (on Windows %USERPROFILE%/.jupyter/jupyter_notebook_config.py):

c.JupyterLabGit.actions = {"post_init": ["touch dummy_init.dat"]}
c.JupyterLabGit.credential_helper = 'cache --timeout=3600'

Or equivalently in $HOME/.jupyter/jupyter_notebook_config.json (on Windows %USERPROFILE%/.jupyter/jupyter_notebook_config.json):

{
  "JupyterLabGit": {
    "actions": {
      "post_init": ["touch dummy_init.dat"]
    },
    "credential_helper": "cache --timeout=3600"
  }
}

Troubleshoot

Before consulting the following list, be sure the jupyterlab_git server extension and the @jupyterlab/git frontend extension have the same version by executing the following commands:

jupyter server extension list
jupyter labextension list

If they do not match or one is missing, please reinstall the package.

the Git panel does not recognize that you are in a Git repository.

Possible fixes:

Be sure to be in a Git repository in the filebrowser tab

Check the server log. If you see a warning with a 404 code similar to: [W 00:27:41.800 LabApp] 404 GET /git/settings?version=0.20.0

Explicitly enable the server extension by running:

jupyter server extension enable --py jupyterlab_git

If you are using JupyterHub or some other technologies requiring an initialization script which includes the jupyterlab-git extension, be sure to install both the frontend and the server extension before launching JupyterLab.

the Git panel is not visible.

Possible fixes:

Check that the JupyterLab extension is installed:

If you don't see @jupyterlab/git v... enabled OK in the list, explicitly install the jupyter labextension by running:

If you see @jupyterlab/git under Uninstalled core extensions: , your installation may have been corrupted. You can run jupyter lab clean --all and reinstall all your extensions.

jupyter labextension install @jupyterlab/git
jupyter labextension list

Contributing

If you would like to contribute to the project, please read our contributor documentation.

JupyterLab follows the official Jupyter Code of Conduct.

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
git clone https://github.com/jupyterlab/jupyterlab-git.git
# Change directory to the jupyterlab-git directory
cd jupyterlab-git
# Install package in development mode
pip install -e ".[dev]"
pre-commit install
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm run build

You 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
jlpm run watch
# Run JupyterLab in another terminal
jupyter lab

With 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, the jlpm run build command 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:

jupyter lab build --minimize=False

To execute the tests

pytest jupyterlab_git
jlpm run test

 

This project follows the all-contributors specification. Contributions of any kind are welcomed!

To add yourself, or someone else, to this list you can either use the bot (@all-contributors please add <username> for <contributions>) or the CLI (jlpm all-contributors add <username> <contributions>).

If you manually edit the .all-contributorsrc config file, run yarn run contributors:generate.


Author: jupyterlab
Source Code: https://github.com/jupyterlab/jupyterlab-git
License: BSD-3-Clause license

#git #jupyterlab