Skip to content

Feature Parity | Normalize extra_labextensions_path precedence across jupyterlab_server and voila #1553

Description

@gauraangkhurana

Problem

The current behavior of extra_labextensions_path is inconsistent across jupyterlab_server and voila repositories.

  1. Within the jupyterlab_server repository the PATH var for looking up extensions is constructed as extra_labextensions_path + labextensions_path
  2. However, in the voila repository the PATH var for looking up extensions is constructed as labextensions_path + extra_labextensions_path

This changes the precedence of extensions lookup. If the same extension exists in both locations, the differing order changes which copy is used, causing surprising behavior depending on the environment.

Proposed Solution

  1. The extra_labextensions_path should be prepended to labextensions_path in both repositories.
  2. It should be constructed like - labextensions_path = extra_labextensions_path + labextensions_path
  3. This makes the behavior consistent across both ecosystems (jupyterlab_server and voila) thus ensuring predictable behavior.

Additional context/ References

  1. jupyterlab_server: labextensions_path
  2. voila labextensions_path

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions