gitignore, ensuring that the project is always managed. The purpose of the prompt is to encourage managed workflow users to add the android and ios directories to the project's. If you'd like, you can disable the check by enabling the environment variable EXPO_NO_GIT_STATUS=1. This prompt is optional and will be skipped when encountered in CI. This is why using the -clean flag is the safest way to use the prebuild command and it is generally recommended in most cases.ĭue to the destructive nature of the flag, you'll be warned to have a clean git status when the -clean flag is used. For example, not all config plugins are idempotent - when your project utilizes a lot of "dangerous modifiers" for performing changes like adding regex changes to application code, this can sometimes lead to unexpected behavior. This is faster than re-generating from scratch, but it may not produce the same results in some cases. When you re-run npx expo prebuild without the -clean flag, it layers the changes on top of your existing files.
The -clean flag will delete any existing native directories before generating.
You can force a specific package manager by providing one of: -npm, -yarn, -pnpm.Īll installations can be skipped by passing the -no-install command, which is useful for testing generation quickly. When the dependencies are changed, prebuild will reinstall packages using the package manager that is currently used in the project (this is inferred from the lockfile). npx expo prebuild -skip-dependency-update react-native,react Package managers
0 kommentar(er)
