I built a CodeSandbox clone while working at Target to facilitate code-sharing around internal component libraries.
Library I was working on to bundle and interpret js files directly in the browser. It didn't actually bundle perse, but it augmented import-maps to support importing data-urls which effectively emulated in-browser bundling. Service workers were another effective approach to this. Service workers could intercept esm imports and send back some local code without ever hitting a remote server.
I once made an editor to augment GitHub gists and make them look like carbon embeds. Basically was a proxy api that would fetch the gist, prepend some css to it based on some query params, and then send back the js to the client. Looked something like <script src="https://supergist.com/malerba118/8bb6f5d15522ea1552c301a70989ada9.js?theme=monokai"></script>
Allow author to define regions of article text that when hovered over or clicked on will highlight some range of lines in the editor.
In edit mode, show author two splitview editors, they can paste version one of the code in left editor and version two in the right editor. When go back to preview mode, will show a github style diff of the two versions of the code.
Allow user to navigate among different code states, and somehow smoothly interpolate between the states (ie, auto-type cahracters at a natural pace). Codehike is doing some interesting work here.
When reader hovers over a heading, could give them an option to copy a link to that heading so they can share that portion of the course with others.
Allow inputs in articles like numeric sliders, text inputs, buttons, whose change events are passed into the sandbox. Allow sanbdox to communicate back to control visual elements within the article but outside of the sandbox.
Allow user to create and embed interactive charts.
Allow authors to upload videos and leave markdown notes at specific times in the timeline.
Provide consistent theming across code editors, terminals, charts, etc. (Something that's hard to do on medium when using a bunch of disparate third party embeds for example)
- Is there a feasible way runwasm could allow dependency imports? As cool as it is to run python in the browser, it's not super useful if you can't include third party deps.
- How big is the team?
- What are the priorities right now and what does roadmap look like?
- Do you have any particular plan to handle backward compatibility? Old courses might break as new features are added. Maybe migrations, maybe versioning the apis and then courses pull the version that they were built on?