Fresh 1.1 – Automatic JSX, plugins, DevTools, and more

Hey folks, author of Fresh here. Very excited for this rather significant release. Happy to answer any questions you may have :)

I've been writing a simple single page form app the past few days and I like Fresh a lot. I really appreciate the simplified project layout vs my last setup of a react app project nestled in a parent express project. It just makes the devops, if you would even called it that, of writing a one-person full stack app easier. Deno running TypeScript without a compile to JS adds to this. I'm happy to see the Preact Signals demo to help manage state between islands in 1.1. Thank you for this great framework. :)

Wow, great work! One question - isn't doing the tailwind processing on every page load pretty CPU intensive? Could you foresee opting-in to that as a build step in the future?

Fresh looks seriously cool! I&#x27;m especially fond of the plugins concept for bringing in compiled assets like Markdown and SCSS. And Getting started with a `deno run` command is very exciting for new-comers too!<p>Shameless-self promotion: I&#x27;ve been working on a similar web framework built on Deno and Cloudflare Workers. It&#x27;s called Keywork[1] and it&#x27;s made for folks who would like to create web apps for the V8 runtime, without getting too attached to a single cloud provider.<p>Keywork has powered all my projects as of recently, but Fresh looks like a serious contender. I would love to chat with the Deno team if they&#x27;re floating around this HN thread! You&#x27;re creating amazing stuff!<p>- [1] <a href="https:&#x2F;&#x2F;keywork.app" rel="nofollow">https:&#x2F;&#x2F;keywork.app</a>

Great update! I wonder if Fresh plans to use Deno&#x27;s (new) HTTP server[1]. Benchmarks for that look incredible (compared to Express).<p>Off-topic but how does the video[2] under Preact Dev Tools look so sharp yet only weight 43KB? Edit: nevermind, the downloaded file&#x27;s 2.9MB. Must be something up with Chrome&#x27;s network tab.<p>[1]: <a href="https:&#x2F;&#x2F;deno.com&#x2F;blog&#x2F;v1.25#new-experimental-http-server-api" rel="nofollow">https:&#x2F;&#x2F;deno.com&#x2F;blog&#x2F;v1.25#new-experimental-http-server-api</a><p>[2]: <a href="https:&#x2F;&#x2F;deno.com&#x2F;fresh-1.1&#x2F;preact_devtools.mp4" rel="nofollow">https:&#x2F;&#x2F;deno.com&#x2F;fresh-1.1&#x2F;preact_devtools.mp4</a>

I just ran this and got a bad cert error. How should I fix it?<p>deno run -A -r <a href="https:&#x2F;&#x2F;fresh.deno.dev" rel="nofollow">https:&#x2F;&#x2F;fresh.deno.dev</a> my-project<p>Sending fatal alert BadCertificate error: error sending request for url (<a href="https:&#x2F;&#x2F;fresh.deno.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fresh.deno.dev&#x2F;</a>): error trying to connect: invalid peer certificate contents: invalid peer certificate: UnknownIssuer

Anybody here used Fresh for a non-toy project yet? Have anecdotal experiences to share?

Is it easy to support other CSS frameworks? I haven’t checked the docs yet.

Is there a plan to allow Vue (and other frameworks) on Fresh? I&#x27;m also looking at Prisma+Deno issue for my dream stack.

Is Fresh primarily a server side rendering tool? Or might it be an option for static-ish webpages hosted by GitHub.io?<p>I love the idea of eliminating lots of build boilerplate but I do ultimately want to output static assets for a read-only webpage.

I seriously cannot wrap around my head how in 2022 people really like JSX and all that X-in-JS crap, it&#x27;s like people doesn&#x27;t know about separation of concerns or clean code at all.