github: add a reproduction environment to the issue template#354
Merged
Conversation
- this should help make reproductions easier as it gives a quick
starting point requiring no boilerplate and is easily accessible from
a browser too
- decided to go with StackBlitz over CodeSandbox and repl.it as it's
WebContainer tech allows for running Node projects entirely _inside_
the browser (via WebAssembly)
- meaning that unlike CodeSandbox and repl.it, their platform doesn't
need to spin up and connect to a container on the backend
- so it's much more efficient, performant, and cost-effective
- and, importantly, it means you don't need an account to get started
with a Node project; you only need an account to save your work etc
- this makes a noticeable UX difference, since user funnels
generally decrease the more steps you take (especially a larger
one like creating an account)
- and we want reproductions to be as easy as possible to create
(so that people actually create them), so optimizing this flow
is important
- that being said, CodeSandbox and repl.it have much stronger OSS
presences and have open-sourced most of their core technology
- and Rollup and rollup/plugins use repl.it for reproductions:
https://replit.com/@rollup/rollup-plugin-repro
- so wanted to use those, but the UX difference was pretty
significant
- repl.it also didn't have as good a DX IMO
- have already made several reproductions of issues using this
environment as well, so can confirm that it works well!
- StackBlitz: https://stackblitz.com/edit/rpt2-repro
- GitHub: https://github.com/agilgur5/rpt2-repro
Repository owner
locked as resolved and limited conversation to collaborators
Sep 4, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a repro env to the issue template to get people to make more repros!
Details
this should help make reproductions easier as it gives a quick starting point requiring no boilerplate and is easily accessible from a browser too
decided to go with StackBlitz over CodeSandbox and repl.it as it's WebContainer tech allows for running Node projects entirely inside the browser (via WebAssembly)
rollup/pluginsuse repl.it for reproductions: https://replit.com/@rollup/rollup-plugin-reproStackBlitz: https://stackblitz.com/edit/rpt2-repro
GitHub: https://github.com/agilgur5/rpt2-repro
READMEwith directions there as well as in theindex.tsfile 🙂References
Have already made several reproductions of issues using this environment as well, so can confirm that it works well!
semantic error TS2339: Property 'write' does not exist on type 'Clipboard'-- can't repro #306 (comment)tsc-- can't repro, Vite misconfiguration #305 (comment)semantic error TS2339: Property 'name' does not exist on type 'User'with rpt2 but nottscwhen using Vite -- can't repro #297 (comment)syntax error TS1068: Unexpected token. A constructor, method, accessor, or property was expected.-- can't repro #247 (comment)@ts-nochecknot working on.tsxfile -- needs TS 3.7+ #223 (comment)