Add a command to enable the extension manager

[jtpio]

This adds the Enable Extension Manager command to the command palette and the main menu.

It can sometimes be a bit difficult to figure out how to enable the extension manager.
Having it exposed as a command should make it more accessible and simplify the steps listed in the docs.

[jupyterlab-dev-mode]

Thanks for making a pull request to JupyterLab!

To try out this branch on binder, follow this link:

[jtpio]

Or maybe the plan for 1.0 is to enable it by default?

[afshin]

cc: @vidartf @tgeorgeux

I think because there isn't yet a story for what to do about extensions that are front-end + back-end, this feature is disabled by default. I don't have a problem with making it easier to discover, but maybe we should add the word "experimental" or something. What do Vidar and Tim think?

[ian-r-rose]

The other reason this was a bit hidden was that we didn't want users to have to install node in order to install lab. So we wanted to hide it a bit until we at least had some feature-detection for node on the frontend.

[jasongrout]

Also, there was still some concern about messaging to users that we do not vet these extensions in any way.

[blink1073]

We already have a way to tell if node is available on the client:

jupyterlab/packages/application-extension/src/index.tsx

Line 137 in 84d6eca

if (builder.isAvailable && builder.shouldCheck) {

jupyterlab/packages/services/src/builder/index.ts

Line 34 in 84d6eca

return PageConfig.getOption('buildAvailable').toLowerCase() === 'true';

I think with that check this PR should go in along with #6277 that solves the companion install piece.

[blink1073]

Agreed that it should still be disabled by default so we can hit the user with that warning dialog.

[jtpio]

@blink1073 the last commit (0b1a40d) checks if the builder is available, and disables the command otherwise:

[jtpio]

So now the current state is as follows:

• the extension manager is disabled by default
• the command to enable the extension manager is only enabled if the builder (node) is available
• if the builder is available (node is installed), and the user decides to enable the extension manager, the warning popup (same as before) shows up and the extension manager can be enabled

Should we also add the word "experimental" (or similar) as @afshin suggested? For example: "Enable Extension Manager (experimental)"

[jasongrout]

Should we also add the word "experimental" (or similar) as @afshin suggested? For example: "Enable Extension Manager (experimental)"

+1. The more caveats the better at this stage, I think.

[jasongrout]

Thanks. This looks good to me now!

[jasongrout]

Congrats on your first merge, @aschlaep!

[blink1073]

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related discussion.