You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blogposts/2022-11-30-announcing-align-deps.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ Let's break down the changes:
87
87
88
88
-**`customProfiles` is now `presets`** — previously, you could only specify a single preset to augment the default one. With the new config schema, you can now list any number of presets, and even exclude the built-in one! This opens up for completely custom presets, and for built-in community presets (like this preset that [only includes new-arch compatible libraries](https://github.com/microsoft/rnx-kit/pull/1877)). As before, this flag is entirely _optional_. If you omit it, the default built-in preset, `microsoft/react-native`, will be used.
89
89
90
-
*Remember that `align-deps` will automatically migrate your existing configs if you add `--migrate-config` when you run it. The old configuration will still work, but it is officially deprecated.*
90
+
_Remember that `align-deps` will automatically migrate your existing configs if you add `--migrate-config` when you run it. The old configuration will still work, but it is officially deprecated._
91
91
92
92
Further, to keep things consistent, we also had to make equivalent changes to a couple of command line flags:
93
93
@@ -97,7 +97,7 @@ Further, to keep things consistent, we also had to make equivalent changes to a
97
97
98
98
Other command line flags have not been changed in any significant ways. Overall, if you are curious about how the new changes work, have a read through the [RFC](https://github.com/microsoft/rnx-kit/blob/rfcs/text/0001-dep-check-v2.md#summary) where we originally discussed this new approach.
99
99
100
-
We've also improved error messages in a number of places to make it more obvious what went wrong where. There is always more that can be improved, so feel free to [file an issues](https://github.com/microsoft/rnx-kit/issues/new/choose) or tell us about your experience and ideas [with a discussion](https://github.com/microsoft/rnx-kit/discussions).
100
+
We've also improved error messages in a number of places to make it more obvious what went wrong where. There is always more that can be improved, so feel free to [file an issue](https://github.com/microsoft/rnx-kit/issues/new/choose) or tell us about your experience and ideas [with a discussion](https://github.com/microsoft/rnx-kit/discussions).
101
101
102
102
## Concluding
103
103
@@ -107,6 +107,8 @@ We are already seeing great usage across some key monorepos within Microsoft, an
107
107
108
108
We are committed in making it a foundational stone for the community developer experience, and you can learn about some interesting ideas for the future and how it might [help migrating to the new architecture](https://github.com/microsoft/rnx-kit/issues/1863) in the rnx-kit repository. Feel free to share your ideas and experiences there too!
109
109
110
+
We cannot wait to hear your experience with `align-deps` - happy coding!
111
+
110
112
---
111
113
112
114
Remember that you can also follow us on Twitter [@ReactNativeMSFT](https://twitter.com/reactnativemsft) to keep up to date on news, feature roadmaps, and more.
0 commit comments