denoland / denoland/deploy_feedback
[FR] Add support for command line parameter configuration in Playgrounds
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I've had a good time using playgrounds to learn Deno and make some PR's to improve support for it...
However, I'm finding the lack of Dynamic imports and not being able to change network access quite limiting, as I can't write code that works both on Node and Deno. Deno.stderr(...) is not the same as node one, and many packages require swaps... but there's no way to do that or test that in playgrounds. Meanwhile, https://vite.new/vue-ts has very few limits and is faster. Runkit's has similar limitations but their UI more than makes up for it with automatic console log with one click, and the ability to split a run pipeline into chunks and run them manually as needed.
I've had a handful of bad experiences with Deno in the past, as my old comments can attest, so I'm glad to finally have a good run.
P.S. This was one of my weekend's project... https://dash.deno.com/projects/dude-get-a-framework
I only just got it running... not sure how many features have issues.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Playgrounds experience and the requested command-line parameter configuration. The issue names dynamic imports and network access as limitations but does not identify files, tests, supported parameters, or acceptance criteria; clarify those requirements before implementation. Done should include an agreed configuration behavior and a way to test it in Playgrounds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100