Skip to content

fix(expo): set output to single to avoid rendering errors #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
d3lm merged 1 commit into from
Feb 13, 2025
Merged

fix(expo): set output to single to avoid rendering errors #61

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion bolt-expo/app.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
},
"web": {
"bundler": "metro",
"output": "static",
"output": "single",
Copy link
Contributor

@d3lm d3lm Feb 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the deployment to Netlify still work with this?

Copy link
Member Author

@Nemikolh Nemikolh Feb 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it does. With this the behaviour is:

single outputs a Single Page Application (SPA), with a single index.html in the output folder, and has no statically indexable HTML

(docs: https://docs.expo.dev/versions/latest/config/app/#output)

"favicon": "./assets/images/favicon.png"
},
"plugins": ["expo-router"],
Expand Down