gatsby: [gatsby develop] Exiting via Ctrl-C leaves terminal/shell in a bad state (Linux/Mac)

Description

When exiting gatsby develop via ^C, the terminal is almost always left in a noecho state. I have observed this on MacOS and Linux both.

Steps to reproduce

Run gatsby develop. After it has entered the server loop, hit ^C. Terminal is no longer echoing prompts, etc. back to the console. Running either tset or reset is required.

Expected result

Terminal should return to the state it was in before gatsby changed it.

Actual result

Terminal is unusuable.

Environment

System: OS: Linux 3.13 Ubuntu 14.04.6 LTS, Trusty Tahr CPU: (12) x64 Intel® Core™ i7-5820K CPU @ 3.30GHz Shell: 4.3.11 - /bin/bash Binaries: Node: 12.6.0 - /home/linuxbrew/.linuxbrew/bin/node npm: 6.9.0 - /home/linuxbrew/.linuxbrew/bin/npm Languages: Python: 2.7.6 - /usr/bin/python Browsers: Chrome: 76.0.3809.100 Firefox: 66.0.3 npmPackages: gatsby: ^2.13.42 => 2.13.42 gatsby-cli: ^2.7.21 => 2.7.21 gatsby-image: ^2.2.7 => 2.2.7 gatsby-plugin-manifest: ^2.2.4 => 2.2.4 gatsby-plugin-mdx: ^1.0.18 => 1.0.18 gatsby-plugin-offline: ^2.2.4 => 2.2.4 gatsby-plugin-optimize-svgs: ^1.0.3 => 1.0.3 gatsby-plugin-react-helmet: ^3.1.2 => 3.1.2 gatsby-plugin-sharp: ^2.2.9 => 2.2.9 gatsby-plugin-styled-components: ^3.1.2 => 3.1.2 gatsby-plugin-typography: ^2.3.2 => 2.3.2 gatsby-remark-images: ^3.1.10 => 3.1.10 gatsby-source-filesystem: ^2.1.6 => 2.1.6 gatsby-transformer-sharp: ^2.2.5 => 2.2.5