The nebula.gl project has migrated to deck.gl-community/editable-layers

[ibgreen]

nebula.gl has been forked into the deck.gl-community repo.

• Future work will be done in https://visgl.github.io/deck.gl-community/docs/modules/editable-layers.
• The new discussion channel for the deck.gl-community repo is in the OpenJS slack

[cfecherolle]

Hi! I was looking for a way to use https://www.npmjs.com/package/react-map-gl-draw with React 17 and react-map-gl but it's not compatible with React > 16, is this something that might be included in future work? Is react-map-gl-draw included in this fork?
Thank you!

[ibgreen]

@cfecherolle As you can read in the table in the linked deck.gl-community documentation page, react-map-gl-draw was not included in the fork.

• This decision was made to simplify the code base with the hope of making it easier for non-dedicated maintainers to keep the deck.gl layers version of nebula.gl alive.
• Given that the new version is no longer broken into deck.gl independent modules, it may not be easy to add.

If it helps, react-map-gl-draw is a small module and you could probably bring the source code into your app and bump the react dependency.

[timnyborg]

@ibgreen do you have any intention of triaging the existing PRs on this repo, or should those of us with open fixes just port them across as new PRs on the deck.gl-community repo?

[ibgreen]

do you have any intention of triaging the existing PRs on this rep

@timnyborg

• I wish the core vis.gl team had the bandwidth to do that, but no. Simply getting the fork into a good shape has been heavy work for multiple contributors.
• I also don't want to oversell the fork. While maintainers of other components have been willing to chip in and modernize build systems, dependencies etc, there is still no single thought leader or owner of the @deck.gl-community/editable-layers module, who can definitely answer whether a specific complex change is reasonable or not. This makes it harder to accept certain PRs etc.
• So opening the same issues in the new repo is no guarantee of attention. However, the issues in this repo are almost certainly not going to be looked at.

[geraldo]

Thanks for your work! So what would be the recommended approach for a new project using editable-layers with latest deck.gl v9? I'm not sure if the advances described at visgl/deck.gl-community#38 mean that editable-layers is functional from the new deck.gl-community repo. Should I go with the staled nebula.js EditableGeojsonLayer module or got with the new forked one?

[ibgreen]

So what would be the recommended approach for a new project using editable-layers with latest deck.gl v9? I'm not sure if the advances described at visgl/deck.gl-community#38 mean that editable-layers is functional from the new deck.gl-community repo. Should I go with the staled nebula.js EditableGeojsonLayer module or got with the new forked one?

What we can say is:

• nebula.gl is for all intents and purposes dead. Contributors have been locked out from merging. I would not expect any further development, including a port to v9. We have asked if the repo could be archived by the owner, but no response.
• editable-layers is an attempt to get the community to continue to maintain the key parts of nebula. It has been ported to deck.gl v9. It would be your best at this time.

[charlieforward9]

It would be smart to archive this repo and make a little mention of the new package in the README. Thank you for continuing to maintain this in its new location!