Changes in mod-compiler.js

8a424beb - [lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)

Fri, 11 Aug 2023 07:31:41 +0000

[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)Why --- Prettier 3 is out. Add support for it with this linter config. **Note for reviewer:** the first commit is the one with the actual changes. The rest of this PR are changes to get the linter passing (mostly autofix). How --- Update eslint-config-prettier and eslint-plugin-prettier. To address deprecation warnings, also update typescript-eslint/parser and typescript-eslint/eslint-plugin. Because of an update to typescript-eslint/parser, we need to suppress deprecation warnings (documented in a comment). Regenerated test snapshots. Due to the upgraded dependencies, typecasts and optional chaining are now auto-fixable by lint. This converts warnings into autofixes. Test Plan --- `yarn test` in the linter config. Run `expotools check --all --fix-lint --no-build --no-test --no-uniformity-check` to try this config on the whole repo. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/config-plugins/build/plugins/mod-compiler.js

42d6b312 - refactor(config-plugins): add existing native files ignore option (#23165)

Fri, 30 Jun 2023 21:46:37 +0000

refactor(config-plugins): add existing native files ignore option (#23165)# Why Part of ENG-8481 This option helps to align the entitlements more to what users would expect. With this, we can fetch the entitlements without the native files, if the user has gitignored them. > Note, this is an opt-in and does not change the default behavior. # How - Added opt-in option `ignoreExistingNativeFiles` to `evalModsAsync` # Todo In EAS CLI, we already know if the user has ignored certain paths. With this feature, we can enable this option (with the proper warnings and opt-out if they need to). See: https://github.com/expo/eas-cli/pull/1906 # Test Plan See added tests. > **Note** > I created the glob mocks by using the vscode launch config, and added a breakpoint whenever an "unexpected" glob was used. By doing that through vscode, I could quickly find all globs that were executed for this test. See config below if you want to try it too.

vscode launch config

```json { "configurations": [ { "name": "Test mods", "request": "launch", "runtimeArgs": ["jest", "--verbose", "withIosBaseMods"], "runtimeExecutable": "yarn", "cwd": "${workspaceFolder}/packages/@expo/config-plugins", "skipFiles": ["/**"], "type": "node", "console": "integratedTerminal", "internalConsoleOptions": "neverOpen" } ] } ```

# Checklist - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). List of files: /expo/packages/@expo/config-plugins/build/plugins/mod-compiler.js

edc75823 - feat(config plugins): better support out of tree support (#22209)

Wed, 26 Apr 2023 19:04:49 +0000

feat(config plugins): better support out of tree support (#22209)# Why Fix various validation issues when using `nexpo prebuild --platform windows --template https://github.com/microsoft/react-native-windows-samples/tree/main/samples/AppServiceDemo` # How # Test Plan # Checklist - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/config-plugins/build/plugins/mod-compiler.js

ed94abb0 - fix(config-plugins): default to `['dangerous']` sort order when using unknown platforms (#22224)

Fri, 21 Apr 2023 17:52:03 +0000

fix(config-plugins): default to `['dangerous']` sort order when using unknown platforms (#22224)# Why Follow-up of #22201 # How When using arbitrary platforms, like `foobar`, the sort order is not defined. This results in errors like: ![image](https://user-images.githubusercontent.com/1203991/233685476-24afd065-77a5-4f39-9d09-a49c20dd7b4f.png) Instead, this change adds a default sorting order of `['dangerous']` when using arbitrary platforms. # Test Plan - Clone the example repository: https://github.com/byCedric/custom-prebuild-example - Create a tarball from template `$ cd ./template && npm pack` - Run `$ expo prebuild --platform macos --template ../template/custom-prebuild-template-1.0.0.tgz` This should not fail as the screenshot above. # Checklist - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). List of files: /expo/packages/@expo/config-plugins/build/plugins/mod-compiler.js

ee216927 - [config-plugins] Rebuild JS files

Mon, 21 Nov 2022 12:46:28 +0000

[config-plugins] Rebuild JS files List of files: /expo/packages/@expo/config-plugins/build/plugins/mod-compiler.js

082815dc - chore: migrate config, config-plugins, config-types, prebuild-config (#17958)

Tue, 28 Jun 2022 00:09:27 +0000

chore: migrate config, config-plugins, config-types, prebuild-config (#17958) List of files: /expo/packages/@expo/config-plugins/build/plugins/mod-compiler.js