Replies: 1 comment 1 reply
-
In the context of there being "platform specific" config (generally speaking), then #28 seems to be tangentially related. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Suggested in #36
Request for an RFC to explore having platform-specific config values, which is particularly relevant if configuration values would ride along with installed packages as implied by #59.
Implementation is relatively straightforward, but the following bikesheds need to be addressed:
process.platform
, or are there others?platform: win32
section would provide config overrides for windows, andplatform: !win32
would provide config overrides for non-windows. Would we need version comparisons, or other things if we're filtering based on node version etc?platform: !win32
and then laterplatform: darwin
, do we prioritize the most specific, or is it order-dependent? (Note that order dependency is particularly fraught when dealing with JS objects, where key order can be munged without realizing it.)Straw proposal to go from:
Beta Was this translation helpful? Give feedback.
All reactions