Fixing package.json dependencies #2
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
react-native and react-native-windows were specified as devDependencies, but they are actually required at runtime not just to build reactxp. This was causing an issue also in the sample app, since
npm run start
wouldn't work because react-native wouldn't exist in node_modules. An alternative is to specify react-native and react-native-windows as peerDependencies, if we want users to be able to choose a range, and include them as dependencies in the sample app. But if we want to lock down what versions they use, having a direct dependency is probably fine.Also the sample app had a bunch of packages in its dependencies section which didn't need to, since they're already direct dependencies of reactxp and so they're already pulled on
npm install