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
When osc-bridge is installed on the system with npm i -g osc-bridge or run via npx, it would be nice to still be able to specify the options. However the way the options are currently being read doesn't work in those cases (even by creating a package.json in the current directory).
It would be nice to be able to pass a path to a config.json that has the same shape as package.config.osc-bridge, so that the tool can be used more effectively standalone.
The text was updated successfully, but these errors were encountered:
s-ol
linked a pull request
Feb 6, 2022
that will
close
this issue
Many thanks for this proposal and the Pull Request. I'll check it in next week, as I am currently on the road with limited Internet connexion and only a tablet.
When
osc-bridge
is installed on the system withnpm i -g osc-bridge
or run vianpx
, it would be nice to still be able to specify the options. However the way the options are currently being read doesn't work in those cases (even by creating a package.json in the current directory).It would be nice to be able to pass a path to a
config.json
that has the same shape aspackage.config.osc-bridge
, so that the tool can be used more effectively standalone.The text was updated successfully, but these errors were encountered: