Jeroen Peeters

**Is your feature request related to a problem? Please describe.** handy for contributors **Describe the solution you'd like** see title **Describe alternatives you've considered** manual... lol

Since jspm support for Deno is way in the future for now, this will probably have to be done manually or through the Dreg project (denofn/dreg). Ultimately this would allow...

prettier and code editors shouldn't be loaded in immediately, and neither should the same resource be loaded in *every time*. Thus the solution is two fold: - [ ] add...

Edit registry and execution dockerfiles to pull deno-alpine from github registry

- [ ] Also allow delete option in Registry UI

Pretty sure this will scale better once moving to a swarm or load balanced instances. - [ ] check incoming request that's not api/static and check if it's a registered...

These files need testing: ## Execution - [x] `handleProxy.ts` obsolete with new library - [ ] `index.ts` split `attachHandlers` in separate file to make testable, the rest doesn't need any...

Visibility of functions will still be ALL, but more people can manage the functions. Make `usr` a csv store and add endpoint in API / mgmt in UI

Something like `lerna version` but for Deno would be nice. But I see it the following way: - [x] ~register files that indicate denoFn versions (`execution/deps.ts`, `registry/deps.ts`, `templates/bundle.ts`)~ - [x]...

It's a mess right now, I'm already adding several todo's as issues instead of in the Readme. I prefer keeping it as .md files in a docs folder, but I'm...