chore: bring over tutorial (without content)

[dummdidumm]

Copied over the technical side of things almost verbatim, replaces the old tutorial. stuff in lib is organized slightly different to the learn.svelte repo (because we now have other stuff in the lib folder, too).

The webcontainers don't load for me yet locally, not sure why.

Other questions:

• there's middleware.js in the learn.svelte repo, do we need to bring that over? What does it do? Does it need to be at the root of the repo or the app project (hopefully the latter)?
• same for vercel.json

Todos:

• playwright tests need to be brought over (only makes sense once the app actually builds)
• check if we need something from the static folder

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
omnisite	❌ Failed (Inspect)			Jun 12, 2024 1:39pm

[dummdidumm]

@Rich-Harris could you check if web container boots up correctly for you locally? If so I'm tempted to merge this to keep the diff somewhat under control, and then iteratively work towards getting the app actually building (with the content etc)

[Rich-Harris]

If I copy over the common.zip and unzip.cjs files then I get as far as this:

Not sure yet what's missing for it to start the app

[dummdidumm]

Yeah same for me, it gets stuck in the ready state, the iframe never starts firing the messages to the parent window which the output tab uses to remove the loading state. Something inside the iframe seems to not be set up correctly

[dummdidumm]

resolved the mystery, the stub I put in was incomplete/wrong. Works now. Looking into what else I need to bring over now.

[Rich-Harris]

Nice! I was thinking we'd put the content in the same place as everything else, so we can have a unified approach to search etc (obviously it'll involve some finagling to get the actual code bits of the exercises working). I'll open a PR to move the content to the root now

[Rich-Harris]

(the existing content, I mean)

[dummdidumm]

yeah sounds good, I'll not do the content stuff in here. I'll see if I can bring over the playwright tests and then merge this

[dummdidumm]

ok playwright tests are so unbearably slow because of the webcontainer bootup that I don't think it's worth it bringing them over now, they will just fail all the time. We should investigate that separately.