Contribute the features back to upstream `open`?

[karlhorky]

Contribute the features back to upstream `open`?

[michaellzc]

@karlhorky Hi, sorry for the late reply, school can get real stressful in summer :(

The incentive of this package is driven by gatsbyjs/gatsby#6550

here's why I hesitate to contribute it back to opn:

@m-allanson I think reuseing the same tab is really a web development specific thing, e.g. http://localhost:8000 and opn isn’t just for opening an URL in browser, it also supprts stuffs like image, text file and more options.

Originally posted by @ExiaSR in gatsbyjs/gatsby#6550 (comment)

that said, I am definitely open to contribute back to upstream if there is need

[karlhorky]

sorry for the late reply, school can get real stressful in summer :(

No worries, thanks for the reply!

I am definitely open to contribute back to upstream if there is need

@sindresorhus actually mentioned in sindresorhus/open#31 (emphasis mine):

You could probably use AppleScript to achieve what you want, but that's way out of scope for this module.

I've asked if this is still the status quo.

---

reuseing the same tab is really a web development specific thing
opn isn’t just for opening an URL in browser, it also supprts stuffs like image, text file and more options

Ah interesting, good points.

Then I guess for this reason I would suggest renaming this module to something that doesn't infer that this is a superset of the other module ("better"). For me it was confusing, at least.

What I would see as a good angle would be to market it as a standalone (zero dependency) version of react-dev-utils/openBrowser. The following code works well, but it has problems with dependency hell.

const openBrowser = require('react-dev-utils/openBrowser');
openBrowser('http://localhost:6006');