Aggiornare expo-build-properties da 57.x a 58.x
Confronto dell’API pubblica di expo-build-properties 57.0.22 e 58.0.10, calcolato automaticamente dai tipi TypeScript. Una firma modificata è una possibile modifica incompatibile, non una certezza.
Riepilogo
| Percorsi di import rimossi | 0 |
|---|---|
| Export rimossi | 0 |
| Firme modificate | 0 |
| Membri di classi o interfacce rimossi | 0 |
| Membri di classi o interfacce modificati | 0 |
| Nuove deprecazioni | 0 |
| Requisiti cambiati (engines, dipendenze peer) | 0 |
| Nuovi export | 0 |
Export rimossi
Nessuna rilevata.
Firme modificate
Nessuna rilevata.
Membri di classi o interfacce rimossi
Nessuna rilevata.
Membri di classi o interfacce modificati
Nessuna rilevata.
Nuove deprecazioni
Nessuna rilevata.
Requisiti cambiati (engines, dipendenze peer)
Nessuna rilevata.
Changelog tra queste versioni
Testo pubblicato dagli autori del pacchetto, mostrato così com’è.
58.0.10
### Patch Changes
- Bump `semver` to `^7.7.4`. ([#50391](https://github.com/expo/expo/pull/50391) by [@hassankhan](https://github.com/hassankhan))58.0.9
### Patch Changes
- Force-bump all packages, due to migration to changesets. ([#50762](https://github.com/expo/expo/pull/50762) by [@kitten](https://github.com/kitten))
- Updated dependencies. ([#50762](https://github.com/expo/expo/pull/50762))
- @expo/schema-utils@58.0.158.0.8
_This version does not introduce any user-facing changes._58.0.7
_This version does not introduce any user-facing changes._58.0.6
_This version does not introduce any user-facing changes._58.0.5
### 🎉 New features
- Add `android.buildExpoModulesCoreFromSource` to compile the `expo-modules-core` native libraries from source instead of using the prebuilt ones. ([#50452](https://github.com/expo/expo/pull/50452) by [@lukmccall](https://github.com/lukmccall))58.0.4
_This version does not introduce any user-facing changes._58.0.3
### 🐛 Bug fixes
- [iOS] Let `ios.enableSceneSupport` adopt the scene lifecycle when another config plugin has inserted lines into the startup block, such as `@react-native-firebase/app`. ([#50221](https://github.com/expo/expo/pull/50221) by [@alanjhughes](https://github.com/alanjhughes))58.0.2
### 🎉 New features
- Add `ios.enableSceneSupport` to adopt the UIKit scene lifecycle in SDK 57 projects. The property is a no-op on SDK 58 and newer. ([#50205](https://github.com/expo/expo/pull/50205) by [@alanjhughes](https://github.com/alanjhughes))58.0.1
_This version does not introduce any user-facing changes._58.0.0
### 🐛 Bug fixes
- [Android] Make `buildReactNativeFromSource` idempotent so repeated prebuilds no longer append a duplicate `includeBuild(expoAutolinking.reactNative)` block to `settings.gradle` (and toggling it off removes the block). ([#46713](https://github.com/expo/expo/pull/46713) by [@ahmdshrif](https://github.com/ahmdshrif))
- [Android] Make the precompiled header reusable by passing `-Xclang -fno-pch-timestamp`, so ccache can reuse it across builds. ([#46915](https://github.com/expo/expo/pull/46915) by [@lukmccall](https://github.com/lukmccall))
- [Android] Pin the C++ dialect of PCH consumer targets to `-std=c++20`. ([#47788](https://github.com/expo/expo/pull/47788) by [@gabrieldonadel](https://github.com/gabrieldonadel))
### 💡 Others
- [Android] Compile the precompiled header once in a shared owner target and reuse it across all codegen targets, instead of building a separate PCH per target. ([#46915](https://github.com/expo/expo/pull/46915) by [@lukmccall](https://github.com/lukmccall))Dai questi dati al tuo agente IA
Vigia è un server MCP gratuito: il tuo agente di programmazione verifica versioni, modifiche incompatibili e vulnerabilità prima di scrivere codice. Senza registrazione né chiave API.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Aggiungi a CursorAggiungi a VS Code★ Stella su GitHub
Qualsiasi altro client MCP
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Skill per agenti (SKILL.md): dice all'agente quando usare Vigia · GitHub Action per le pull request
Domande frequenti
Quali sono le modifiche incompatibili aggiornando expo-build-properties da 57 a 58?
Tra expo-build-properties 57.0.22 e 58.0.10, Vigia ha trovato 0 export rimossi, 0 firme modificate e 0 membri di classi o interfacce rimossi o modificati.
Cosa è stato deprecato in expo-build-properties 58?
0 export o membri risultano ora deprecati in expo-build-properties 58.0.10.
Per gli agenti
GET https://vigia.coredls.cloud/v1/packages/npm/expo-build-properties/upgrade?from=57.0.22&to=58.0.10