Add semicolons after Flow type expressions to restore syntax highlighting

[calcsam]

Our lack of semicolons on Flow Type expressions like eg type Plugin = { name: string, } (see eg https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/redux/actions.js#L77) causes syntax highlighting to fail in Sublime Text, as documented in babel/babel-sublime#309. If we add semicolons in, highlighting works again.

A couple screenshots from my local environment:

Without semicolon:

With semicolon:

[KyleAMathews]

We're a semicolon-less repo. Not sure adding semicolons in a handful of spots to workaround a bug in a editor's syntax highlighting makes sense?

[emwalker]

Since there are repos that do not use semicolons, a better approach would be to fix the syntax highlighting rules for flow, as seen here:

babel/babel-sublime#309 (comment)

[KyleAMathews]

👍