Hi TinkerPop, With the recent work on gremlin-javascript by Jorge [1], I see no reason for the "gremlin" package currently published on npmjs.org [2] to continue to exist as a distinct project. Newcomers would be so confused, and I don't think fragmentation is a good idea here. I think it should be replaced by the official gremlin-javascript GLV that is being developed here. I'm ok to transfer/donate the "gremlin" package name to the Apache TinkerPop project if we think it's a good idea to use that name.
However, the current "gremlin" JS package has been mentioned by some implementers (Microsoft Azure CosmosDB [3]), so maybe we want to sync with them first so they get a chance to update their documentation/examples considering there will be several breaking changes. Maybe I can help on that. Also, there shouldn't be issues with versions since I only published on the v2.x branch there (npmjs package versions are basically immutable). The GLV can safely be published there as 3.3.x and 3.2.x once ready. I think I can flag previously published versions as "deprecated" so people get soft warnings when attempting to install these, encouraging them to upgrade to the official GLV (need to check that). Jean-Baptiste [1] https://github.com/apache/tinkerpop/pull/695 [2] npmjs.com/package/gremlin [3] https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-nodejs
