Skip to content

Pin ipyvue<1.12.0 to fix maplibre in Google Colab#1311

Merged
giswqs merged 1 commit intomasterfrom
fix-ipyvue-colab
Mar 21, 2026
Merged

Pin ipyvue<1.12.0 to fix maplibre in Google Colab#1311
giswqs merged 1 commit intomasterfrom
fix-ipyvue-colab

Conversation

@giswqs
Copy link
Copy Markdown
Member

@giswqs giswqs commented Mar 21, 2026

Summary

  • Pin ipyvue<1.12.0 in requirements.txt and pyproject.toml maplibre extras to fix broken maplibre widgets in Google Colab
  • ipyvue 1.12.0 was published to PyPI but the corresponding jupyter-vue@1.12.0 npm package was never published, causing a 404 when Colab loads widget JS from jsdelivr CDN

Related

Test plan

  • Open a Google Colab notebook
  • !pip install leafmap[maplibre] and verify pip show ipyvue returns version < 1.12.0
  • Run import leafmap.maplibregl as maplibre; m = maplibre.Map(); m and confirm the map renders without widget errors

ipyvue 1.12.0 was published to PyPI but the corresponding jupyter-vue
1.12.0 npm package was never published. This causes a 404 when Colab's
widget manager tries to load the JS from jsdelivr CDN, breaking all
ipyvuetify-based widgets.

Upstream issue: widgetti/ipyvue#105
Copilot AI review requested due to automatic review settings March 21, 2026 19:15
@giswqs giswqs merged commit 50d2675 into master Mar 21, 2026
16 checks passed
@giswqs giswqs deleted the fix-ipyvue-colab branch March 21, 2026 19:16
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Pins ipyvue to avoid broken MapLibre widgets in Google Colab caused by an ipyvue 1.12.0 / missing jupyter-vue@1.12.0 npm release mismatch.

Changes:

  • Add ipyvue<1.12.0 to requirements.txt (base dependencies).
  • Add ipyvue<1.12.0 to the maplibre optional-dependency extra in pyproject.toml.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File Description
requirements.txt Adds an upper-bound pin for ipyvue in the project’s base install requirements.
pyproject.toml Adds the same ipyvue pin to the maplibre extra dependencies.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

pmtiles = ["pmtiles", "flask", "flask-cors"]
ai = ["geopandas", "osmnx", "localtileserver>=0.10.4", "rastervision", "pytorch-lightning", "torchgeo"]
maplibre = ["anywidget", "geopandas", "fiona", "h3", "ipyvuetify", "localtileserver", "mapclassify", "maplibre>=0.3.1", "pmtiles", "rioxarray", "xarray"]
maplibre = ["anywidget", "geopandas", "fiona", "h3", "ipyvue<1.12.0", "ipyvuetify", "localtileserver", "mapclassify", "maplibre>=0.3.1", "pmtiles", "rioxarray", "xarray"]
Copy link

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ipyvue<1.12.0 is now specified both in the base dependencies (requirements.txt) and again in the maplibre extra. Since [tool.setuptools.dynamic].dependencies already pulls in requirements.txt for every install (including leafmap[maplibre]), this duplication is redundant and creates a risk of the two constraints drifting. Prefer keeping the constraint in a single place (either base deps or the extra), and add a short comment pointing to the upstream issue so it’s clear when the pin can be removed.

Suggested change
maplibre = ["anywidget", "geopandas", "fiona", "h3", "ipyvue<1.12.0", "ipyvuetify", "localtileserver", "mapclassify", "maplibre>=0.3.1", "pmtiles", "rioxarray", "xarray"]
# Note: ipyvue version is pinned in requirements.txt due to an upstream ipyvue<1.12.0 compatibility issue.
# Do not repeat the pin here; keep it centralized in requirements.txt so it can be updated in one place.
maplibre = ["anywidget", "geopandas", "fiona", "h3", "ipyvuetify", "localtileserver", "mapclassify", "maplibre>=0.3.1", "pmtiles", "rioxarray", "xarray"]

Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown

@github-actions github-actions bot temporarily deployed to pull request March 21, 2026 19:20 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants