fix: Bumping Serve Up to 9.2.0 Broke Calls to Serve's API

[trvsysadmin]

Follow Up on:

#6546

69125cc

Apologies in advance if some things are lacking, not super familiar with gatsby code base yet. I tested locally for v1 and it was fine.

In particular:

• is directory still needed? See https://github.com/zeit/serve-handler#public-string
• is open still needed?

[KyleAMathews]

Deploy preview for using-postcss-sass failed.

Built with commit 5c88c9b

https://app.netlify.com/sites/using-postcss-sass/deploys/5b517139b13fb17317b6526b

[KyleAMathews]

Deploy preview for gatsbyjs failed.

Built with commit 5c88c9b

https://app.netlify.com/sites/gatsbyjs/deploys/5b517138b13fb17317b65263

[gatsbybot]

Deploy preview for gatsbygram failed.

Built with commit 5c88c9b

https://app.netlify.com/sites/gatsbygram/deploys/5b517138b13fb17317b65265

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit 5c88c9b

https://deploy-preview-6598--using-drupal.netlify.com

[KyleAMathews]

Yeah, you can run gatsby serve --open. We should use something like https://www.npmjs.com/package/openurl to restore opening the URL after it's started.

[KyleAMathews]

We don't need directory because serve defaults to using the current working directory as the base? E.g. you don't need an absolute path anymore?

[trvsysadmin]

Directory Question

Yes it seems to be so as far as this description: https://github.com/zeit/serve-handler#public-string

By default, the current working directory will be served. If you only want to serve a specific path, you can use this options to pass a custom directory to be served relative to the current working directory.

For example, if serving a Jekyll app, it would look like this:

{
  "public": "_site"
}

My test on v1 works with the public hardcoded string.

[trvsysadmin]

Dash Dash Open Option

• I checked the current package.json and opn is already there
• openurl dies for me via "GPU Process Fail" or something like that - I am on a ubuntu16 latest Chrome
• opn has no such issue.

[KyleAMathews]

Thanks!

[gatsbot]

Holy buckets, @trvsysadmin — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (Currently we’ve got a couple t-shirts available, plus some socks that are really razzing our berries right now.)
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. You’ll receive an email shortly asking you to confirm. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!