230407/Fluxup_PAP
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

first commit

Browse Source
This commit is contained in:
230407
2026-03-10 16:18:05 +00:00
commit 11f9c069b5
31635 changed files with 3187747 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
node_modules/@expo/config-plugins/README.md generated vendored Normal file
View File

@@ -0,0 +1,34 @@
<!-- Title -->
<h1 align="center">
👋 Welcome to <br><code>@expo/config-plugins</code>
</h1>
<p align="center">A powerful tool for generating native app code from a unified JavaScript interface.</p>
<p align="center">
<img src="https://flat.badgen.net/packagephobia/install/@expo/config-plugins">
<a href="https://www.npmjs.com/package/@expo/config-plugins">
<img src="https://flat.badgen.net/npm/dw/@expo/config-plugins" target="_blank" />
</a>
</p>
<!-- Body -->
Most basic functionality can be controlled by using the [static Expo config](https://docs.expo.dev/versions/latest/config/app/), but some features require manipulation of the native project files. To support complex behavior we've created config plugins, and mods (short for modifiers).
For more info, please refer to the official Expo docs: [Config Plugins](https://docs.expo.dev/config-plugins/introduction/).
## Environment Variables
### `EXPO_DEBUG`
Print debug information related to static plugin resolution.
### `EXPO_CONFIG_PLUGIN_VERBOSE_ERRORS`
Show all error info related to static plugin resolution. Requires `EXPO_DEBUG` to be enabled.
### `EXPO_USE_UNVERSIONED_PLUGINS`
Force using the fallback unversioned plugins instead of a local versioned copy from installed packages, this should only be used for testing the CLI.