Merge branch 'master' into lighthouse

.bumpversion.cfg

@@ -0,0 +1,19 @@
+[bumpversion]
+current_version = 1, 0, 2, 'final', 0
+commit = False
+tag = False
+parse = (?P<major>\d+)\,\ (?P<minor>\d+)\,\ (?P<patch>\d+)\,\ \'(?P<release>\S+)\'\,\ (?P<build>\d+)
+serialize = 
+	{major}, {minor}, {patch}, '{release}', {build}
+
+[bumpversion:part:release]
+optional_value = final
+values = 
+	alpha
+	candidate
+	final
+
+[bumpversion:part:build]
+
+[bumpversion:file:jupyterlab/_version.py]
+

.eslintignore

@@ -17,6 +17,8 @@ dev_mode/workspaces
 examples/app/build
 examples/app/themes
 examples/app/schemas
+examples/chrome-example-test.js
 tests/**/coverage
 docs/_build
 docs/api
+!dev_mode/static/index.out.js

.eslintrc

@@ -7,7 +7,7 @@
   "extends": ["eslint:recommended", "prettier"],
   "plugins": ["prettier"],
   "parserOptions": {
-    "ecmaVersion": 6,
+    "ecmaVersion": 2017,
     "sourceType": "module",
     "ecmaFeatures": {
       "modules": true,

.github/ISSUE_TEMPLATE/installation-and-configuration-issues.md

@@ -3,4 +3,4 @@ name: Installation and configuration issues
 about: Installation and configuration assistance
 ---
 
-If you are having issues with installation or configuration, you may ask for help on the [JupyterLab Gitter channel](https://gitter.im/jupyterlab/jupyterlab) or file an issue here.
+If you are having issues with installation or configuration, we encourage you to post in the [Jupyter Discourse forum](https://discourse.jupyter.org/c/jupyterlab) or file an issue here.

.github/pull_request_template.md

@@ -1,4 +1,26 @@
-Fixes #
+<!--
+Thanks for contributing to JupyterLab!
+Please fill out the following items to submit a pull request.
+See the contributing guidelines for more information:
+https://github.com/jupyterlab/jupyterlab/blob/master/CONTRIBUTING.md
+-->
 
-**Screenshots**
-If applicable, add before and after screenshots to help show the issue being fixed, or the appearance of a new feature.
+## References
+
+<!-- Note issue numbers this pull request addresses (should be at least one, see contributing guidelines above). -->
+
+<!-- Note any other pull requests that address this issue and how this pull request is different. -->
+
+## Code changes
+
+<!-- Describe the code changes and how they address the issue. -->
+
+## User-facing changes
+
+<!-- Describe any visual or user interaction changes and how they address the issue. -->
+
+<!-- For visual changes, include before and after screenshots here. -->
+
+## Backwards-incompatible changes
+
+<!-- Describe any backwards-incompatible changes to JupyterLab public APIs. -->

.gitignore

@@ -2,16 +2,21 @@ MANIFEST
 build
 dist
 lib
+
+jupyterlab/imports.css
 jupyterlab/static
 jupyterlab/schemas
 jupyterlab/themes
 jupyterlab/geckodriver
+
 dev_mode/schemas
 dev_mode/static
 dev_mode/themes
 dev_mode/workspaces
 dev_mode/stats.json
 
+packages/nbconvert-css/style/
+
 packages/theme-*/static
 node_modules
 .cache
@@ -46,3 +51,5 @@ lerna-debug.log
 yarn-error.log
 
 junit.xml
+
+*.tsbuildinfo

.prettierignore

@@ -19,4 +19,5 @@ examples/app/schemas
 tests/**/coverage
 docs/_build
 docs/api
-**/package.json
+**/package.json
+.eggs

CONTRIBUTING.md

@@ -4,20 +4,22 @@ If you're reading this section, you're probably interested in contributing to
 JupyterLab. Welcome and thanks for your interest in contributing!
 
 Please take a look at the Contributor documentation, familiarize yourself with
-using JupyterLab, and introduce yourself on the mailing list and share
-what area of the project you are interested in working on. Please see also the
-Jupyter [Community Guides](https://jupyter.readthedocs.io/en/latest/community/content-community.html).
+using JupyterLab, and introduce yourself to the community (on the mailing list
+or discourse) and share what area of the project you are interested in working
+on. Please also see the Jupyter [Community Guides](https://jupyter.readthedocs.io/en/latest/community/content-community.html).
 
 We have labeled some issues as [good first issue](https://github.com/jupyterlab/jupyterlab/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) or [help wanted](https://github.com/jupyterlab/jupyterlab/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
 that we believe are good examples of small, self-contained changes.
 We encourage those that are new to the code base to implement and/or ask
 questions about these issues.
 
-## Tag Issues with Labels
+If you believe you’ve found a security vulnerability in JupyterLab or any
+Jupyter project, please report it to
+[[email protected]](mailto:[email protected]). If you prefer to encrypt your
+security reports, you can use [this PGP public
+key](https://jupyter-notebook.readthedocs.io/en/stable/_downloads/ipython_security.asc).
 
-Users without the commit rights to the jupyterlab repository can also tag the issues with labels. For example: To apply the label `foo` and `bar baz` to an issue, comment `@meeseeksdev tag foo "bar baz"` on the issue.
-
-## General Guidelines
+## General Guidelines for Contributing
 
 For general documentation about contributing to Jupyter projects, see the
 [Project Jupyter Contributor Documentation](https://jupyter.readthedocs.io/en/latest/contributor/content-contributor.html) and [Code of Conduct](https://github.com/jupyter/governance/blob/master/conduct/code_of_conduct.md).
@@ -39,8 +41,24 @@ installing a prettier
 extension for your code editor and configuring it to format your code with
 a keyboard shortcut or automatically on save.
 
+## Submitting a Pull Request Contribution
+
+Generally, an issue should be opened describing a piece of proposed work and the
+issues it solves before a pull request is opened. This lets community members
+participate in the design discussion, makes others aware of work being done, and
+sets the stage for a fruitful community interaction. A pull request should
+reference the issue it is addressing.
+
+### Tag Issues with Labels
+
+Users without the commit rights to the JupyterLab repository can tag issues with
+labels using the `@meeseeksdev` bot. For example: To apply the label `foo` and
+`bar baz` to an issue, comment `@meeseeksdev tag foo "bar baz"` on the issue.
+
 ## Setting Up a Development Environment
 
+You can launch a binder with the latest JupyterLab master to test something (this may take a few minutes to load): [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyterlab/jupyterlab/master?urlpath=lab-dev/)
+
 ### Installing Node.js and jlpm
 
 Building JupyterLab from its GitHub source code requires Node.js.
@@ -69,7 +87,7 @@ If you use `conda`, you can install notebook using:
 conda install -c conda-forge notebook
 ```
 
-You may also want to install `nb_conda_kernels` to have a kernel option for different [conda environments](http://conda.pydata.org/docs/using/envs.html)
+You may also want to install `nb_conda_kernels` to have a kernel option for different [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html)
 
 ```bash
 conda install -c conda-forge nb_conda_kernels
@@ -136,9 +154,11 @@ jupyter lab --dev-mode
 ```
 
 Development mode ensures that you are running the JavaScript assets that are
-built in the dev-installed Python package. When running in dev mode, a red
-stripe will appear at the top of the page; this is to indicate running
-an unreleased version.
+built in the dev-installed Python package. Note that when running in dev mode,
+extensions will not be activated by default.
+
+When running in dev mode, a red stripe will appear at the top of the page;
+this is to indicate running an unreleased version.
 
 ### Build and Run the Tests
 
@@ -192,8 +212,8 @@ jlpm create:test <package-directory-name>
 #### Running Jest Tests
 
 For those test folders that use `jest`, they can be run as `jlpm test` to run the files
-directly. You can also use `jlpm test --namePattern=<regex>` to specify specific test
-suite names, and `jlpm test --pathPattern=<regex>` to specify specific test module names. In order to watch the code, add a `debugger` line in your code and run `jlpm watch`. This will start a node V8 debugger, which can be debugged
+directly. You can also use `jlpm test --testNamePattern=<regex>` to specify specific test
+suite names, and `jlpm test --testPathPattern=<regex>` to specify specific test module names. In order to watch the code, add a `debugger` line in your code and run `jlpm watch`. This will start a node V8 debugger, which can be debugged
 in Chrome by browsing to `chrome://inspect/` and launching the remote session.
 
 ## Performance Testing
@@ -520,7 +540,10 @@ a package by importing from it in the TypeScript file, and then running:
 `jlpm run integrity` from the repo root.
 
 We also have scripts for creating and removing packages in `packages/`,
-`jlpm run create:package` and `jlpm run remove:package`.
+`jlpm run create:package` and `jlpm run remove:package`. When creating a package,
+if it is meant to be included in the core bundle, add the `jupyterlab: { coreDependency: true }`
+metadata to the `package.json`. Packages with `extension` or `mimeExtension` metadata
+are considered to be a core dependency unless they are explicitly marked otherwise.
 
 ## Testing Changes to External Packages
 

jupyterlab/CORPORATE.md → CORPORATE.md

@@ -28,7 +28,7 @@ happy and healthy requires a ton of work and money.
 
 Working in a yard full of puppies is CRAZY! At times, there can be a line around
 the block of people wanting to play with the puppies and talk, or complain, to
-the maintainers. Sometimes, people show up wth more puppies. These are like pull
+the maintainers. Sometimes, people show up with more puppies. These are like pull
 requests to an open-source project. While the maintainers love puppies and would
 love to be able to have more of them for everyone to enjoy, each new puppy has
 to be cleaned, fed, trained, taken to the vet, etc.

README.md

@@ -8,11 +8,13 @@
 # [JupyterLab](http://jupyterlab.github.io/jupyterlab/)
 
 [![PyPI version](https://badge.fury.io/py/jupyterlab.svg)](https://badge.fury.io/py/jupyterlab)
-[![Build Status](https://travis-ci.org/jupyterlab/jupyterlab.svg?branch=master)](https://travis-ci.org/jupyterlab/jupyterlab)
+[![Downloads](https://pepy.tech/badge/jupyterlab/month)](https://pepy.tech/project/jupyterlab/month)
 [![Build Status](https://dev.azure.com/jupyterlab/jupyterlab/_apis/build/status/jupyterlab.jupyterlab?branchName=master)](https://dev.azure.com/jupyterlab/jupyterlab/_build/latest?definitionId=1&branchName=master)
 [![Documentation Status](https://readthedocs.org/projects/jupyterlab/badge/?version=stable)](http://jupyterlab.readthedocs.io/en/stable/)
-[![Google Group](https://img.shields.io/badge/-Google%20Group-lightgrey.svg)](https://groups.google.com/forum/#!forum/jupyter)
-[![Join the Gitter Chat](https://img.shields.io/gitter/room/nwjs/nw.js.svg)](https://gitter.im/jupyterlab/jupyterlab)
+[![GitHub](https://img.shields.io/badge/issue_tracking-github-blue.svg)](https://github.com/jupyterlab/jupyterlab/issues)
+[![Discourse](https://img.shields.io/badge/help_forum-discourse-blue.svg)](https://discourse.jupyter.org/c/jupyterlab)
+[![Gitter](https://img.shields.io/badge/social_chat-gitter-blue.svg)](https://gitter.im/jupyterlab/jupyterlab)
+
 [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/master?urlpath=lab/tree/demo)
 
 An extensible environment for interactive and reproducible computing, based on the
@@ -39,67 +41,27 @@ Read the latest version's documentation on [ReadTheDocs](http://jupyterlab.readt
 
 ### Installation
 
-[install](http://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html) JupyterLab using `conda`, `pip`, or `pipenv`. Conda is recommended if you have no installation preference.
+JupyterLab can be installed using `conda` or `pip`. For more detailed instructions, consult the [installation guide](http://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html).
 
 Project installation instructions from the git sources are available in the [contributor documentation](CONTRIBUTING.md).
 
-#### conda
-
-Conda is an open source package management system and environment management system that runs on Windows, macOS, and Linux. Conda packages and distributes software for any language, and by default uses the Anaconda repository managed by Anaconda Inc. To install conda, please [see the conda installation instructions](https://conda.io/docs/user-guide/install/index.html).
+### conda
 
-Install the [JupyterLab `conda` package](https://anaconda.org/conda-forge/jupyterlab) with:
+If you use `conda`, you can install it with:
 
-```bash
+```shell
 conda install -c conda-forge jupyterlab
 ```
 
-#### pip
-
-pip is a package management system for installing and updating Python packages, and comes with any Python installation. On Ubuntu and Fedora Linux, use the system package manager to install the `python3-pip` package. [\_The Hitchhiker's Guide to Python_provides guidance on how to install Python](https://docs.python-guide.org/starting/installation/); Another option is to [install Python directly from python.org](https://www.python.org/getit/). We suggest you [upgrade pip](https://pip.pypa.io/en/stable/installing/) before using it to install other programs.
-
-JupyterLab requires Python 3.5 or higher.
-
-1.  When using Windows with Python version 3.5 or higher, use the [Python Launcher for Windows](https://docs.python.org/3/using/windows.html?highlight=shebang#python-launcher-for-windows) to use `pip` with Python version 3:
-    ```bash
-    py -3 -m pip install jupyterlab
-    ```
-2.  If the system has a `python3` command (standard on Unix-like systems), install with the comand:
-    ```bash
-    python3 -m pip install jupyterlab
-    ```
-3.  Using the `python` command directly is another option, but this will use the _current_ version of Python (which may be Python version 2 or version 3 if both are installed):
-    ```bash
-    python -m pip install jupyterlab
-    ```
-
-Some systems have a `pip3` command that has the same effect as `python3 -m pip` and/or a `pip` command that behaves the same as `python -m pip`.
-
-Adding `--user` after `pip install` will install the files to a local user install directory (typically `~/.local/` or `%APPDATA%\Python` on Windows) instead of the system-wide directory. This can be helpful, especially if writing to the system-wide directory is not permitted. However, the user-level `bin` directory must be added to the `PATH` environment variable in order to launch `jupyter lab`.
-
-#### pipenv
-
-`Pipenv` provides users and developers of applications with an easy method to setup a working environment, however Python must be installed first. See the [pipenv installation documentation](https://docs.pipenv.org/install) to use Pipenv if it is not installed.
-
-`pipenv` can be installed as:
-
-```bash
-pipenv install jupyterlab
-pipenv shell
-```
+### pip
 
-or from a git checkout:
+If you use `pip`, you can install it with:
 
-```bash
-pipenv install git+git://github.com/jupyterlab/jupyterlab.git#egg=jupyterlab
-pipenv shell
+```shell
+pip install jupyterlab
 ```
 
-When using `pipenv`, in order to launch `jupyter lab`, activate the project's virtualenv. For example, in the directory where `pipenv`'s `Pipfile` and `Pipfile.lock` live (i.e., where the above commands were run):
-
-```bash
-pipenv shell
-jupyter lab
-```
+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`.
 
 #### Installing with Previous Versions of Jupyter Notebook
 
@@ -171,7 +133,7 @@ JupyterLab's current maintainers are listed in alphabetical order, with affiliat
   architecture).
 - Jason Grout, Bloomberg (co-creator, vision, general development).
 - Fernando Perez, UC Berkeley (co-creator, vision).
-- Ian Rose, UC Berkeley (Real-time collaboration, document architecture).
+- Ian Rose, Quansight/City of LA (general core development, extensions).
 - Saul Shanabrook, Quansight (general development, extensions)
 - Steven Silvester, JPMorgan Chase (co-creator, release management, packaging,
   prolific contributions throughout the code base).
@@ -187,5 +149,16 @@ To be listed, please submit a pull request with your information.
 
 ## Getting help
 
-We encourage you to ask questions on the [mailing list](https://groups.google.com/forum/#!forum/jupyter),
-and participate in development discussions or get live help on [Gitter](https://gitter.im/jupyterlab/jupyterlab). Please use the [issues page](https://github.com/jupyterlab/jupyterlab/issues) to provide feedback or submit a bug report.
+We encourage you to ask questions on the [Discourse forum](https://discourse.jupyter.org/c/jupyterlab). A question answered there can become a useful resource for others.
+
+Please use the [GitHub issues page](https://github.com/jupyterlab/jupyterlab/issues) to provide feedback or submit a bug report.
+
+### 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 to listen in.
+
+- When: Wednesdays [9AM Pacific Time](https://www.thetimezoneconverter.com/?t=9%3A00%20am&tz=San%20Francisco&)
+- Where: [`calpoly/jupyter` Zoom](https://calpoly.zoom.us/my/jupyter)
+- What: [Meeting notes on Dropbox Paper](https://paper.dropbox.com/doc/JLab-Dev-Meeting-Minutes-2019--AZlv6L3jnv8ntl6kJK88y5M5Ag-Lj0P4kI2JrbA0eXHZSdY5)