forked from zulip/zulip-mobile
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
deps: Follow @react-native-{community -> async-storage}/async-storage…
… move. This seems to be a move / rename, not something more disruptive like a rewrite. In fact, I don't expect this to be any more disruptive than taking the next patch version in the library's natural progression. If I add the new-location package at its first available version, 1.13.0, and I keep the old one at its latest available (and the one we're on currently), 1.12.1, I see very few differences between them: git diff --no-index \ node_modules/@react-native-{community,async-storage}/async-storage The package in its new location keeps the changelog entries from when it was maintained at the old location. That changelog confirms that 1.13.0 comes right after 1.12.1, and the 1.13.0 entry looks like a match for what we saw in the `git diff --no-index` output. So this shouldn't be disruptive at all, unless 1.13.0 has unannounced breaking changes. [1] For the output, see <insert link here>
- Loading branch information
1 parent
d5fce7f
commit 4018b19
Showing
9 changed files
with
17 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 2 additions & 2 deletions
4
...-native-community/async-storage_v1.x.x.js → ...ive-async-storage/async-storage_v1.x.x.js
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters