There is a new pull request by st3r4g against master on the void-packages repository

https://github.com/st3r4g/void-packages bumblebee-modulepath
https://github.com/void-linux/void-packages/pull/17933

bumblebee: set correct MODPATH_NVIDIA after libglvnd switch
This simple change results in a working bumblebee setup in a `mesa`/`nvidia390` Optimus laptop. After the switch to `libglvnd`, `bumblebee` can be setup correctly because `nvidia390` doesn't attempt to replace `mesa` anymore. Enabling the `bumblebeed` service makes Xorg pick up Mesa's GLX by default, while apps run with `optirun` use NVIDIA's GL. Arch has an additional [patch](https://git.archlinux.org/svntogit/community.git/tree/trunk/0008-libglvnd.patch?h=packages/bumblebee) for `libglvnd` support which sets the __GLVND_DISALLOW_PATCHING env variable but I didn't find it necessary, maybe it got fixed in a recent `libglvnd` update. If someone else finds that necessary, we can include it.
Tested on a Optimus laptop with `mesa`/`nvidia390` configuration (but should also work for `mesa`/`nvidia`, although NVIDIA's Prime Render Offload is a much better method performance-wise).

A patch file from https://github.com/void-linux/void-packages/pull/17933.patch is attached