Closed bitnot closed 5 years ago
@vladikoff could you kindly take a look?
Good stuff 👍 Would like to see this merged as open.appName
not working is an issue for me.
A suggestion for this PR: is it worth updating the readme to point to opn instead of open?
Also, opn
allows you to specify a string or array for options.app
- array to pass arguments to the app so the documentation should probably reflect that 😄
This needs a rebase, no unrelated style changes and no unrelated version changes.
Thanks for looking into this @XhmikosR! Not sure if I should update the version and change log, please advise.
@bitnot: no you shouldn't update any meta files, this is done when a new release is made.
@bitnot: can you skip README.md inclusion? We usually update it when we make the release.
@XhmikosR
I was a bit concerned users may try passing opn
-style config with app
instead of appName
and with unsupported options
, so felt need to clarify in the ReadMe.
Thanks for merging!
Will be in v2.0.0 when that is made.
Maybe you could add a test?
I am not very good with node, but I will try to add a test.
Any release date in mind?
It doesn't depend on me otherwise I'd made the release already. I don't have access to this npm package, so when https://github.com/gruntjs/grunt-contrib-connect/pull/252 is merged.
Fixes #229 by passing open:appName config property to opn and calling open:callback.