Fresh 1.1 – Automatic JSX, plugins, DevTools, and more • Hacker News Board

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

#41

Post by MarkBennett » Thu, Sep 08, 2022, 5:26 PM UTC

lucacasonato wrote: post #21

rough-sea wrote: post #9

Earlier quoted context omitted.

https://deno.com/blog/fresh-1.1#experimental-denoserve-suppo... Just use --unstable to enable it.

You also need to pass a `experimentalDenoServe: true` option in the options bag passed to `start()` in your `main.ts` file. I forgot to add this to the post initially. Have retroactively added it now :)

Are there any benchmarks with the new server yet? Would be keen to see how it compares to the existing server as benchmarking on my machine showed a significant improvement over the existing http server in stdlib.

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

#42

Post by Waterluvian » Thu, Sep 08, 2022, 5:30 PM UTC

Is Fresh primarily a server side rendering tool? Or might it be an option for static-ish webpages hosted by GitHub.io?

I love the idea of eliminating lots of build boilerplate but I do ultimately want to output static assets for a read-only webpage.

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

#43

Post by winrid » Thu, Sep 08, 2022, 5:35 PM UTC

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?

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

#44

Post by rough-sea » Thu, Sep 08, 2022, 5:36 PM UTC

Waterluvian wrote: post #42

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

It’s a server-side framework that delivers static content - but the static content is rendered just in time rather than ahead of time.

For ahead of time static sites in Deno, check out Packup https://packup.deno.dev/

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

#45

Post by Waterluvian » Thu, Sep 08, 2022, 5:39 PM UTC

rough-sea wrote: post #44

Waterluvian wrote: post #42

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

It’s a server-side framework that delivers static content - but the static content is rendered just in time rather than ahead of time. For ahead of time static sites in Deno, check out Packup https://packup.deno.dev/

Ahhh gotcha. So unlikely to be a good fit for my needs.

Thanks!

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

#46

Post by lucacasonato » Thu, Sep 08, 2022, 6:26 PM UTC

verdverm wrote: post #30

lucacasonato wrote: post #27

Earlier quoted context omitted.

Are you behind a corporate firewall? Can you set `DENO_TLS_CA_STORE=system` and try again?

Is deno using a custom cert store by default? --- https://deno.com/blog/v1.13#use-system-certificate-store-for...

It uses the Mozilla certificate store by default.

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

#47

Post by pier25 » Thu, Sep 08, 2022, 9:24 PM UTC

rough-sea wrote: post #44

Waterluvian wrote: post #42

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

It’s a server-side framework that delivers static content - but the static content is rendered just in time rather than ahead of time. For ahead of time static sites in Deno, check out Packup https://packup.deno.dev/

AFAIK the static content is cached somehow with Fresh/Deno. It's not compiled on every request.

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

#48

Post by lucacasonato » Thu, Sep 08, 2022, 11:21 PM UTC

teebot wrote: post #33

lucacasonato wrote: post #2

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

I really want to try fresh together with edgedb. Any chance a builtin authentication will be added soon? Or is there a recipe to implement something like auth0?

One of the next releases will improve the plugin API to the point where authentication providers can be very easily added as plugins.

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

#49

Post by babyshake » Thu, Sep 08, 2022, 11:59 PM UTC

gibbonsrcool wrote: post #17

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 Signal…

How does it compare to using Next? Looking through the Fresh docs I don't see references to an ORM, mutations, etc. I'm probably missing or misunderstanding something.

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

#50

Post by e_y_ » Fri, Sep 09, 2022, 2:04 AM UTC

jakelazaroff wrote: post #36

verdverm wrote: post #31

Earlier quoted context omitted.

Isn't className custom DSL in React? Vue's concepts in the v-* are more pleasant than the React way, imho. Learning a bit of DAL is not a blocker for me, given how many tools already require this

No, `className` is the DOM property exposed to JavaScript that corresponds to the `class` attribute in HTML: https://developer.mozilla.org/en-US/docs/Web/API/Element/cla...

React JSX mostly uses JS DOM property naming (className, style, tabIndex) but converts a few HTML-style attributes (data-, aria-)