Thanks for your thoughts! I do adore Fresh. In fact, I have run production projects on Next.js and Remix, and played around with Deno Fresh, and I enjoy them in different ways.

When I wrote "no build", I simply meant that we do not bundle the whole app into a single file.

Fresh is indeed very close to what I'm trying to explore here, yet if I understand correctly about Fresh, we still need a real build step: https://fresh.deno.dev/docs/concepts/server-configuration#-b...

Disclaimer: I have nothing against build steps, I just wish to explore an alternative approach where we completely do without them!

Thanks for the reply! I don't quite understand why you want to avoid a build step. Normally when people talk about that what they really mean is they don't want to have to run a build command, but you still have that.

To put it another way, what is the downside of Fresh's build step that you avoid?

Ah please don't get me wrong, there's no build command in my example. The command to start the app directly is: `deno src/main.ts`

and `main.ts` is an original source file, it's not a "bundle" of many files together, like in other setups with build config (tsconfig, webpack config, babel config, etc.)

I wouldn't call Fresh build step a downside either. With build step, there comes a build config (https://fresh.deno.dev/docs/concepts/server-configuration#-b...).

Imo, Fresh' build config is already way simpler than the "traditional" webpack approach (https://deno.com/blog/node-config-hell). Here in FullSoak, I only wish to push this boundary further ie. "no build config at all".