Can we do a partial rollout? If so what would be needed when?
Can we determine if the code in the editor requires Skulpt packages dynamically? (i.e. can we automatically utilise pyodide where appropriate and rollout indirectly?)
Can we add pyodide to the web component?
Fixes required
Input function asks for the answer before it tells you what the question is 😰
Fix the chart.add function in pygal to accept a single value for the values argument as well as a list of values 📊
Work out why the whls won’t load up on the staging site 🛞
Stop the SenseHat resetting on every run 🔁
Reduce latency between code runs by caching the modules interpreted from WebAssembly so this does not need to happen each time the code is run, possibly using a WebAssembly Module (see thread) ⏱️
Remaining tasks outstanding:
crossorigin
will need to be added to cross-domain resources once the HTTP headers are addedsqlite3
so we can add a UI wrapper around itOriginally posted in https://github.com/RaspberryPiFoundation/editor-ui/issues/893
Considerations:
Fixes required