build(expo-plugins): leave plugin source/tsconfig in published package #5795
+3
−9
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.
This way users may rebuild it from source if the need to for some reason
Related issues
Noticed this when a community member wanted to add expo config plugin code to Notifee, based on react-native-firebase and it turns out we weren't shipping the source here invertase/notifee#190
Release Summary
Conventional commit, should not actually generate a release on it's own but next release will have source
Test Plan
yarn pack
inpackages/app
that this has the desired effect:Think
react-native-firebase
is great? Please consider supporting the project with any of the below:React Native Firebase
andInvertase
on Twitter