denoland / denoland/deploy_feedback
Requirements for JSX runtime for Deno Deploy
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I see fresh listed as the JSX runtime of choice.
Even though it is documentation only in the end, should there be a process for defining Deno Deploy "compatible" JSX runtimes? Maybe a requiremenet for complete encapsulation?
Couple of examples for another JSX runtime for Deno:
```typescript
const { h } = await import("https://cdn.skypack.dev/@virtualstate/x");
const { render } = await import("https://cdn.skypack.dev/@virtualstate/dom");
await render(h("Hello World"), document.body);
```
Using https://deno.land/x/deno_dom/deno-dom-wasm.ts :
```bash
deno run \
--import-map=https://cdn.skypack.dev/@virtualstate/deno/import-map.json \
https://cdn.skypack.dev/@virtualstate/deno/lib/example-no-net.js
```
https://github.com/virtualstate/x/blob/main/packages/deno/src/example-no-net.ts
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the compatibility question and the linked @virtualstate/x, @virtualstate/dom, and deno-dom examples, including the referenced example-no-net.ts. Determine whether Deno Deploy needs a defined JSX-runtime process and encapsulation requirement; done means the requirements or decision are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100