Troubleshooting
This site contains some tips to troubleshoot your app in case something doesn’t work as expected.
Update Fresh
The easiest way to resolve most issues is to ensure that you’re on the latest version of Fresh. We continuously work on Fresh and there is a good chance that the issue you’re running into has already been resolved in the latest version of Fresh.
Don’t use esm.sh
Fresh 1.x heavily relied on esm.sh to be able to use npm
packages with Fresh. This continued a bit through the early alpha versions of
Fresh 2. With the move to vite
this is not necessary
anymore and you should use the relevant npm package directly from npm.
{
"imports": {
- "cowsay": "https://esm.sh/cowsay"
+ "cowsay": "npm:cowsay@^1.6.0"
}
}
InfoNot using
esm.sh
solves many issues and footguns with duplicate Preact versions in your app. If you’re seeing strange JavaScript errors in the browser in your app than this is likely the cause.
Attach a debugger
To attach a debugger to vite with Deno run this command:
deno run -A --inspect npm:vite
# or
deno run -A --inspect-brk npm:vite
Debug vite resolution
To debug vite resolution issues run vite with the --debug
flag. This will
print lots of debugging information to the terminal.
Debug vite transformations
To debug vite plugin transformations, use
vite-plugin-inspect
.
This gives you a UI that shows all transformations of all plugins for every
file.