Add issue templates, reference codesandbox starters

[ChristianMurphy]

Issue forms give a more structured flow to filling out bug reports and
feature requests.
Ensuring that information essential to helping resolve issues is
provided mostly upfront, to avoid unnecessary confusion and frustration
for both the reporters and maintainers during triage.

All of the information required in the form was previously required be
the issue template, but could be accidentally erased.

There are also additional optional fields around runtime, package
manager, operating system, and build tools, which are common follow up
questions during triage.

this also adds an optional, but much appreciated, field for a runnable
sandbox to demonstrate issues. Along with some starter templates for
codesandbox.

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

[ChristianMurphy]

/cc @remcohaszing

[wooorm]

fast refresh doesn’t seem to work with Next.js, should that be made possible (probably by having another page in between the content and the app)?

On that page, add something like:

// ⚠️ Important! Please make sure the dependencies are up to date.
// You can refresh them in the Dependencies section (left-bottom on CodeSandbox)

[wooorm]

Care to add a Node.js example? Here’s roughly what I was thinking: https://codesandbox.io/s/gracious-fermi-pzich?file=/index.js. (p.s: for some reason it still thinks there’s a src/index.js, which I moved to index.js, and I’m not sure where that’s configured?)

[ChristianMurphy]

Care to add a Node.js example? Here’s roughly what I was thinking: https://codesandbox.io/s/gracious-fermi-pzich?file=/index.js.

Sure! Added in 0776279

[wooorm]

last nit, perfect otherwise!

[wooorm]

Thanks so much!!