-
Notifications
You must be signed in to change notification settings - Fork 31
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
base: master
Are you sure you want to change the base?
chore: bump deps #285
Conversation
There was a problem hiding this 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.
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'; |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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'
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
"@luma.gl/core": "^9.0.0", | ||
"@luma.gl/engine": "^9.0.0", |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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'; |
There was a problem hiding this comment.
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
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. |
My dependent repo uses deck v9, so I'll aim this PR for 2.0. I am happy to do dig into the |
@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. |
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