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
Currently, there are two dynamic paths available that are include platform and architecture as inputs. However, one includes node version and the other includes the current ABI version. In the use-case I'm currently working on, the same package has to be distributed for all platforms, hence the need for a dynamic path where all of the target binaries can be included. But we don't have control over the end users node version, so using either node version or ABI version is not stable enough.
Would it be possible to add a search path that just has platform and architecture has dynamic components?
The text was updated successfully, but these errors were encountered:
Currently, there are two dynamic paths available that are include platform and architecture as inputs. However, one includes node version and the other includes the current ABI version. In the use-case I'm currently working on, the same package has to be distributed for all platforms, hence the need for a dynamic path where all of the target binaries can be included. But we don't have control over the end users node version, so using either node version or ABI version is not stable enough.
Would it be possible to add a search path that just has platform and architecture has dynamic components?
The text was updated successfully, but these errors were encountered: