Deploying with a Github Action to Deno Deploy is not working with Fresh 1.1.0
See original GitHub issueWhen my project is deployed with my Github Action, I get error like this about h
Here’s a deployment gone wrong fresh-strapi-q1s1v7x99dt0.deno.dev
But if I cut the action out and deploy directly, it all works fine. “Automatic” mode:
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Deno Deploy error · Issue #953 · denoland/fresh - GitHub
I have a website built in Fresh. I didn't touch it for few months, now I just went and changed some CSS, pushed...
Read more >deployctl/README.md at main - GitHub
The Deno Deploy GitHub Action allows for easy deployment to Deno Deploy from a GitHub Actions workflow. This allows a simple way to...
Read more >denoland/fresh: The next-gen web framework. - GitHub
Link the Deno Deploy project to the main.ts file in the root of the created repository. The project will be deployed to a...
Read more >Actions · denoland/fresh - GitHub
The next-gen web framework. Contribute to denoland/fresh development by creating an account on GitHub.
Read more >Issues · denoland/deploy_feedback - GitHub
For reporting issues with Deno Deploy. Contribute to denoland/deploy_feedback development by creating an account on GitHub.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
GitHub Action deployment mode does not support reading
deno.json
yet, which is necessary for automatic JSX, because of thecompilerOptions
in the config file.If you specify the
import-map
key in the Action configuration, that is being respected. If you only configure the import map viadeno.json
though, it won’t be picked up.Similarly, a custom JSX factory already works today if you explicitly specify the
@jsx React.createElement
pragma in all of your component modules.However, I think there’s a case to be made that
deno.json
should be picked up automatically and “just work”, which is what this issue should be about.