Steps to reproduce

• Tell us what broke. The more detailed the better.
• If you can, please create a simple example that reproduces the issue and link to a gist, jsbin, repo, etc. This makes it much easier for us to debug and issues that have a reproducible example will get higher priority.

Examples:

• CodeSandbox.io
  • Dove sandbox
  • https://codesandbox.io/s/github/tdpowerskills/feathers-sandbox
  • Uses VSCode and stock Node.js containers. Containers are regenerated on every boot.
• Glitch.com
  • https://glitch.com/edit/#!/feathers4-sandbox
  • Slower to boot a new fork, but images are saved statefully and your endpoint can be accessed publicly 24/7.
• Feathers client sandbox with Vue
  Repo: https://github.com/tdpowerskills/feathers-sandbox
  

Modifications:

• Helmet configured in config/sandbox.json to allow iFrame embedding from codesandbox.io and glitch
• helmet updated to 4.6 from 4.3.1 ( useDefaults bug was fixed )
• eslint with -fix interferes with built in prettier and causes crashes, removed -fix
• Sandbox config file configured with template: "node" and node: "16". Without this the importer will mistakenly run the code in the react-app template.
• start script fallsback to dev (Glitch only supports start and uses a custom rust/ruby/pnmp server without Yarn)

Similar-ish projects

• https://github.com/nuxt/codesandbox-nuxt
• https://github.com/ember-cli/codesandbox

Expected behavior

An official-ish sandbox should be easy to get running. Creating fully functional running reproducible sandboxes for github issues should take no more than 5 minutes.

Actual behavior

Very few if any exist. CLI generator creates sandboxes with subtle issues which make it non-trivial to DIY.

System configuration

Module versions: dove

NodeJS version: 16 baby

Operating System: iPadOS, Android, Chromebooks, MacOS, Windose

Proposal #1

Create a side project under the feathersjs organization called... starter or sandbox. I can't imagine how to roll this into the monorepo. Having a full repo should make it easier to get this in as a preloaded template. It should obviously regenerate using the CLI and closely track it.

Proposal #2

Create a web UI for generating feathers. The sandbox can be generated in /tmp/feathers and then sync'd to /sandbox. The only dependencies would be a body parser and sync tool like what's being done in the Dove sandbox linked above. Console-feed would not be needed to show progress as a read only server terminal is always visible in CSB and easily accessible in Glitch.