-
Notifications
You must be signed in to change notification settings - Fork 352
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.
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
Support for Expo (React Native for web) apps #333
Comments
hey evan! been watching your RN demos and am very excited you are using netlify! this request is an excellent use case for splitting out detectors from Netlify Dev: https://github.com/netlify/netlify-dev-plugin/tree/master/src/detectors we have been planning for this to be a standalone, reusable feature anyway and just need some work to take out some netlify dev specific assumptions. i think i will need to do some heavy lifting to do this "split out project" and will free up after my conf commitments this week. wont need anything from you in the meantime but thanks for the push. |
any news with this? |
no, sorry. i left the company. feel free to open up a new issue/pr |
- Do you want to request a feature or report a bug?
Feature Request
Now with first-class web support coming to React Native it would be great to have feature detection built into the deployment command.
- What is the current behavior?
expo build:web
to generate a static sitenetlify deploy
starts the flow/web-build
This last step doesn't seem to persist my choice. It'd be cool if it checked to see if the
app.json
(React Native config file) exists in the root directory, then possibly checks to see ifexpo.web.build.output
is defined (custom output path).So if
/web-build
exists andapp.json
exists you would get the following:and if
expo.web.build.output
is defined you would get that value as the auto suggested path.How
I'm happy to work on this PR if you guys are interested.
The text was updated successfully, but these errors were encountered: