You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
When I started this lib there wasn't a known way to run mapbox-gl-js in a non-web-gl browser environment and so I had this mock only mock mapbox-gl-js functionality. Now that there is a solution for running mapbox-gl-js in a non-web-gl environment, should this mock look into being for Node.js only?
The WebGL mock you reference will only work for browsers. mapbox-gl-js should already be able to work headless with the node renderer, at least that's what the gl-js unit tests run with. The project will dynamically swaps in a browser implementation for the default node implemented as part of the browserify config.
There could still be an odd impedance mismatch if draw has a hard dependency on the DOM.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I started this lib there wasn't a known way to run mapbox-gl-js in a non-web-gl browser environment and so I had this mock only mock mapbox-gl-js functionality. Now that there is a solution for running mapbox-gl-js in a non-web-gl environment, should this mock look into being for Node.js only?
Some questions to answer.
/cc @davidtheclark @scothis
The text was updated successfully, but these errors were encountered: