Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: bump deps #285

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

chore: bump deps #285

wants to merge 3 commits into from

Conversation

charlieforward9
Copy link

Tried bumping the most important (primarily those within the visgl org) dependencies up to their latest versions and fixing the build issues that came along with them.

Closes #283

Copy link
Collaborator

@chrisgervang chrisgervang left a comment

Choose a reason for hiding this comment

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

Thank you! This is a great start. I think we'll want to switch to using the MapboxOverlay since MapboxLayer has been deprecated, but it still works as-is we can do that in a follow up PR.

tsconfig.build.tsbuildinfo Outdated Show resolved Hide resolved
package-lock.json Outdated Show resolved Hide resolved
import {MapRef, StaticMap, StaticMapProps} from 'react-map-gl';
import {MapboxLayer} from '@deck.gl/mapbox/typed';
import type {DeckProps, MapViewState} from '@deck.gl/core/typed';
import {MapboxOverlay as MapboxLayer} from '@deck.gl/mapbox';
Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh, this actually isn't a drop-in replacement and will require some changes to work. http://deck.gl/docs/upgrade-guide#deckglmapbox

Copy link
Collaborator

Choose a reason for hiding this comment

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

As a temporary fix I believe we can still import MapboxLayer with import MapboxLayer from '@deck.gl/mapbox/mapbox-layer'

Copy link
Author

@charlieforward9 charlieforward9 Jan 19, 2025

Choose a reason for hiding this comment

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

Rather get this out of the way now. Im not getting any type errors, and all instances in the src/ folder implement the same props {id: ..., ...deck} where id is a string and deck is a Deck obj that may have also been changed in v9 to reflect the change. Let me know.

Copy link
Collaborator

Choose a reason for hiding this comment

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

The API is different in MapboxOverlay. It creates a deck instance rather than getting passed an instance and that inversion would require a bit of refactoring

Copy link
Author

Choose a reason for hiding this comment

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

@chrisgervang

I replaced the deck instance with the deck props in 03a2f0f

I see that the link shows that MapboxLayer to MapboxOverlay shows interleaved: true as the replacement. Should the updated API include this?

@charlieforward9
Copy link
Author

Would this also close #251 and #277?

Comment on lines +55 to +56
"@luma.gl/core": "^9.0.0",
"@luma.gl/engine": "^9.0.0",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Luma 9.1 was released today and refines a lot of the APIs introduced in 9.0 https://luma.gl/docs/whats-new

Copy link
Author

Choose a reason for hiding this comment

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

Are you suggesting we set hubble 2.0 to target luma 9.1?

import {MapRef, StaticMap, StaticMapProps} from 'react-map-gl';
import {MapboxLayer} from '@deck.gl/mapbox/typed';
import type {DeckProps, MapViewState} from '@deck.gl/core/typed';
import {MapboxOverlay as MapboxLayer} from '@deck.gl/mapbox';
Copy link
Collaborator

Choose a reason for hiding this comment

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

The API is different in MapboxOverlay. It creates a deck instance rather than getting passed an instance and that inversion would require a bit of refactoring

@chrisgervang
Copy link
Collaborator

Would this also close #251 and #277?

#251, maybe. #277, not yet since it would require the addition of a MapView with a white clearColor in the PR, I imagine.

@chrisgervang
Copy link
Collaborator

Not all users (e.g. Kepler.gl) are able to upgrade to deck v9 yet, so I'm considering a hubble 1.4 release with support for the latest version of deck v8 and bumping Hubble.gl to 2.0 for deck v9 support.

@charlieforward9
Copy link
Author

charlieforward9 commented Jan 22, 2025

2.0 for deck v9 support

My dependent repo uses deck v9, so I'll aim this PR for 2.0. I am happy to do dig into the MapboxOverlay refactor in the coming days to get that out of the way as well. (Although it strangely does not throw any lint errors when passing deck in as of now)

@charlieforward9
Copy link
Author

charlieforward9 commented Jan 23, 2025

@chrisgervang can we get a 2.0-alpha version released from this PR? Not entirely sure how that'd happen given its monorepo configuration? I'd like to start testing with my dependent application without having to wait for this to land, especially if youre trying to ship a 1.4 version first.

Thank you.

@charlieforward9
Copy link
Author

@chrisgervang what your roadmap for this PR looking like?

I've been waiting to see this land before getting back to the side project I've been looking to enhance with this.

Anything I can help with?

@chrisgervang
Copy link
Collaborator

I'm actively updating all of the examples to use MapboxOverlay.

Then I'll be going through the release process of 1.4, which includes updating dependencies in the existing website and publishing a beta (and assuming all is good, immediately graduating to production).

Then we can upgrade to deck 9 with this PR, and I think it could make sense to bump to 2.0 at that point.

At some point soon I'd like to upgrade the website to use the latest vis.gl docusorus template instead of gatsby since it's a lot less painful to maintain. This can happen in parallel to the releases.

@chrisgervang
Copy link
Collaborator

Hey @charlieforward9 you can merge master in, I don't think they'll be many other changes

@charlieforward9
Copy link
Author

charlieforward9 commented Jan 31, 2025

@chrisgervang Ok, I'll follow your lead. Just keep me in touch and I'll help out.

When you said I can merge master in, what do you mean? I do not have merge access.

@chrisgervang
Copy link
Collaborator

Oh I just meant I've pushed changes to master that you'll need to merge into your branch here

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.

[Bug] Incompatible with deck.gl v9.x , react v18/v19
2 participants