FullSoak Windows

An example FullSoak App that:

• can be developed on Windows platform (with or without Linux subsystem)
• can be developed on Unix platform (e.g. MacOS)
• is deployable to Deno Deploy: https://fullsoak-windows.deno.dev

What's cooking here?

Contrary to official examples for Node.js, Deno, Bun, Cloudflare Workers, this one is intentionally meant to be an unventional take (ie: the path less travelled) when building a FullSoak app.

What's the difference?

In "a traditional FullSoak app", the recommended directory structure is:

fullsoak-app
|_ src
|  |_ components
|  |  |_ Shared
|  |  |  |_ styles.css
|  |  |_ MyComponent
|  |     |_ index.tsx
|  |     |_ styles.css
|  |_ main.ts
|_ deno.jsonc

In this repo, everything feels like a rebellious teenager:

fullsoak-app
|_ ctrl
|  |_ MyController.ts
|_ things
|  |_ Box
|  |  |_ index.tsx
|  |_ MyApp.tsx
|  |_ MyApp.css
|_ deno.jsonc
|_ main.ts

Yet the actual logic in main.ts for both setups remains relatively similar. This proves that the framework itself can handle unconventional usages. However, any unconvenitional (undocumented / unofficial) usage is supported on a best-effort basis, so if you're unsure what you're doing, it's advisable to simply stick to the documented setup.

Other resources

• Project wiki: https://github.com/fullsoak/fullsoak/wiki
• HackerNews discussions: https://news.ycombinator.com/item?id=43029089
• A more elaborate example with simple authentication: https://github.com/fullsoak/guestbook-deno-example