React-Native-Web - From Webpack to Metro config.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 696
- Avg merge
- 8m
- Merged PRs (30d)
- 7
Description
We have installed the new Expo SDK and would like to use the Metro Bundler.
Now we have had a few important configs in the Webpack Config so far, are there also options under Metro?
1. config.output.publicPath = `https://${process.env.AWS_BRANCH}.${process.env.AWS_APP_ID}.amplifyapp.com/`
2. config.output.filename = 'static/js/aivy.js?v=[hash]'
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by locating the Metro configuration entry point and comparing it with the referenced Webpack Config options: output.publicPath and output.filename. Done should clearly document whether Metro supports equivalent settings for the Expo SDK setup, or identify the supported alternatives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native, webpack
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100