[Fresh 2] Deploy Classic fails with ISOLATE_INTERNAL_FAILURE 100%
After upgrading to Fresh 2, deploying to my existing Deno Classic project results in 100% failure with ISOLATE_INTERNAL_FAILURE.
More Context:
1.
vite is able run the dev server without issue.
2. vite build succeed.
3. deno serve -A _fresh/server.js initially fails for it cannot resolve https-proxy-agent, made it work by adding it in build.rollupOptions.external and installing it separately.
4. This project contains cron jobs so moving to EA is not an option yet.
11 Replies
"ISOLATE_INTERNAL_FAILURE" is a generic opaque error. In context of Fresh 2 this is often associated with not updating the entry point to
deno serve -A _fresh/server.js, but that happened here.
"fails for it cannot resolve https-proxy-agent" sounds suspicious. But without seeing the actual code only crude guesswork is possible.tl;dr — We need transparent errors
Unfortunately my project is commercial so I really can’t share the codes.
The opaque nature of deploy classic makes it close to impossible to debug without Deno team’s help in looking up internal logs.
I did try a few blind guesses, sadly it didn’t help.
Worst case scenario, I’ll have to go tedious and bisect-deploy my way up.
I still think this
https-proxy-agent thing is suspicious, you should not have to touch build.rollupOptions.external, but then again I have no real experience with Deno Deploy.
If you can create a minimal reproduction repo and file an issue, that would certainly help (maybe in the main deno repository, as this looks more like a Deno Deploy problem than a Fresh problem)I needed to add
ssr.external for vite to work, I would suspect that the same has to be added to the build process.
Apparently some of my deps, likely CJS, did not survive the rollup transpiling in Fresh 2, when Deno has no problem consuming as-is in Fresh 1.
Worth a try tho, let me post the result here when it’s done.Cleaning up my whole project and the deploy is still failing, I have genuinely lost all clues. Is deploy classic not supporting Fresh 2?
Fresh - The simple, approachable, productive web framework.
Fresh features just-in-time edge rendering, island based interactivity, and zero-configuration TypeScript support. Fast to write; fast to run.
The code is in the Fresh repo -> https://github.com/denoland/fresh/tree/main/www
You can start the website locally after cloning the Fresh repo with
deno task www
I do that all the time when I work on the documentation.Yes! After a few deployment failures and guesswork on the Fresh 2 app and my project, it led me to a missing
--entrypoint=_fresh/server.js in my deploy command.
Let me restore the whole project and try again.
That fixes the issue, thanks!
These opaque errors do create unnecessary frustration, hopefully EA provides more transparent errors when the new cron is out.To be fair, this problem get mentioned in the troubleshooting guide -> https://fresh.deno.dev/docs/advanced/troubleshooting#my-deployment-wont-start
But I'll add this specific error message to make this even more explicit.
Troubleshooting | Fresh docs
Troubleshooting Fresh applications.
It's on me for not crunching through the whole doc, thanks for adding that error code!
I missed that too, as I misread the initial problem description thought that this had been checked.
If my PR gets merged, search engines should pick this error message up and hopefully point others in the right direction if they encounter a similar situation.