Remove fresh.deno.dev #993
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According to the homepage: > Fresh routes are dynamically server-rendered Preact components I can't find anything in the docs that lets you render to static files on disk, and the deployment documentation requires Docker or some other way to run a web server. Fresh looks really neat for building a web server, but does not support the pre-rendering that's core to the Jamstack architecture.
✅ Deploy Preview for jamstack-site ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the homepage:
I can't find anything in the docs that lets you render to static files on disk, and the deployment documentation requires Docker or some other way to run a web server. Fresh looks really neat for building a web server, but does not support the pre-rendering that's core to the Jamstack architecture.
(Have I gravely misunderstood what "pre-rendering" means? Is Jamstack using it to mean "rendering HTML on the server, rather than the client"?)