Actualizar expo-font de 57.x a 58.x
Comparación de la API pública de expo-font 57.0.4 y 58.0.8, calculada automáticamente a partir de sus tipos TypeScript. Una firma modificada es un posible cambio incompatible, no una certeza.
Resumen
| Rutas de importación eliminadas | 0 |
|---|---|
| Exports eliminados | 0 |
| Firmas modificadas | 4 |
| Miembros de clases o interfaces eliminados | 0 |
| Miembros de clases o interfaces modificados | 0 |
| Nuevas deprecaciones | 0 |
| Cambios de requisitos (engines, dependencias peer) | 0 |
| Exports nuevos | 3 |
Exports eliminados
No se detectaron.
Firmas modificadas
| export | Antes | Después |
|---|---|---|
expo-font · useFonts | (map: string | Record<string, any>): [boolean, Error | null] | (map: FontMap): [boolean, Error | null] |
expo-font · loadAsync | (fontFamilyOrFontMap: string | Record<string, any>, source?: any): Promise<void> | (fontFamilyOrFontMap: FontMap, source?: any): Promise<void> |
expo-font · FontResource | { uri?: string | number | undefined; display?: FontDisplay | undefined; default?: string | undefined; testString?: string | undefined; } | { uri?: string | number | undefined; display?: FontDisplay | undefined; default?: string | undefined; weight?: string | number | undefined; style?: "normal" | "italic" | "oblique" | undefined; } |
expo-font · UnloadFontOptions | { display?: FontDisplay | undefined; } | { display?: FontDisplay | undefined; weight?: string | number | undefined; style?: "normal" | "italic" | "oblique" | undefined; } |
Miembros de clases o interfaces eliminados
No se detectaron.
Miembros de clases o interfaces modificados
No se detectaron.
Nuevas deprecaciones
No se detectaron.
Cambios de requisitos (engines, dependencias peer)
No se detectaron.
Exports nuevos (3)
| import | export | kind |
|---|---|---|
expo-font | FontMap | type |
expo-font | FontFaceDefinition | type |
expo-font | FontFamilyDefinition | type |
Changelog entre estas versiones
Texto publicado por los autores del paquete, mostrado tal cual.
58.0.8
### Patch Changes
- [Internal] Bump precompiled artifacts due to ABI breakage in expo-modules-jsi, which makes `JavaScriptValue` a non-copyable struct. ([#51368](https://github.com/expo/expo/pull/51368) by [@tsapeta](https://github.com/tsapeta))58.0.7
### Patch Changes
- Bump precompiled artifacts due to ABI breakage in expo-modules-core@58.0.13. ([#51138](https://github.com/expo/expo/pull/51138) by [@alanjhughes](https://github.com/alanjhughes))58.0.6
### Patch Changes
- Restored the `./plugin` subpath export so typed config plugins can be imported from `<package>/plugin` again. ([#50965](https://github.com/expo/expo/pull/50965) by [@Titozzz](https://github.com/Titozzz))58.0.5
### Patch Changes
- Bump precompiled artifacts due to ABI breakage in expo-modules-jsi@58.0.6. ([#50881](https://github.com/expo/expo/pull/50881) by [@kitten](https://github.com/kitten))58.0.4
### 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))58.0.3
### 🐛 Bug fixes
- [iOS] Keep the previously registered font when a font loaded from a new path has the same PostScript name, instead of unregistering it and crashing on render. ([#50561](https://github.com/expo/expo/pull/50561) by [@eliotgevers](https://github.com/eliotgevers))58.0.2
### 🐛 Bug fixes
- [iOS] Import `UIKit` in the `UIFont` extension, which relied on another file in the module importing it. ([#50277](https://github.com/expo/expo/pull/50277) by [@chrfalch](https://github.com/chrfalch))58.0.1
### 🛠 Breaking changes
- [web] Removed `FontResource.testString`. The CSS Font Loading API detects font loading without a test string. ([#49497](https://github.com/expo/expo/pull/49497) by [@vonovak](https://github.com/vonovak))
### 🎉 New features
- [android][ios] Select a face of a multi-face font family with the `fontWeight` and `fontStyle` style props. ([#49486](https://github.com/expo/expo/pull/49486) by [@vonovak](https://github.com/vonovak))
- Support loading multiple font weights and styles per `fontFamily` in `useFonts`/`loadAsync` on Android, iOS, and web. Use `fontWeight` and `fontStyle` style props to select the correct face. ([#47939](https://github.com/expo/expo/pull/47939) by [@bryanmylee](https://github.com/bryanmylee))
- [web] Accept a variable-font weight range, for example `weight: '100 900'`, on a font face. Android and iOS ignore a range and read the weight from the font file. ([#49487](https://github.com/expo/expo/pull/49487) by [@vonovak](https://github.com/vonovak))
### 💡 Others
- [web] Replaced the `fontfaceobserver` dependency with the CSS Font Loading API, so `loadAsync` also waits for the font on Safari and iOS browsers. ([#49497](https://github.com/expo/expo/pull/49497) by [@vonovak](https://github.com/vonovak))58.0.0
### 🛠 Breaking changes
- [ios] `getLoadedFonts()` no longer reports the PostScript name read out of a font loaded with `loadAsync`, only the name (the alias) it was loaded under. ([#48432](https://github.com/expo/expo/pull/48432) by [@vonovak](https://github.com/vonovak))
### 🎉 New features
- [android] Added an `axes` field to the config plugin's font definitions, so one variable font file can also back a slanted or condensed face through its `slnt`, `wdth` and other variation axes. ([#48621](https://github.com/expo/expo/pull/48621) by [@vonovak](https://github.com/vonovak))
- [android] Support variable weight fonts in the config plugin ([#48129](https://github.com/expo/expo/pull/48129) by [@L65FREAD](https://github.com/L65FREAD))
- [ios] Apply `fontWeight` to variable fonts loaded with `useFonts`. ([#48432](https://github.com/expo/expo/pull/48432) by [@vonovak](https://github.com/vonovak))
### 🐛 Bug fixes
- [android] Apply `fontWeight` and `fontStyle` to fonts loaded with `useFonts`, instancing a variable font's `wght` axis at each weight. Bold and italic text previously fell back to a system font. ([#48129](https://github.com/expo/expo/pull/48129) by [@L65FREAD](https://github.com/L65FREAD))
- [iOS] Fixed `renderToImageAsync` reporting the main screen's scale rather than the scale the image was rendered at. ([#48172](https://github.com/expo/expo/pull/48172) by [@alanjhughes](https://github.com/alanjhughes))
- [web] Fixed `isLoaded()` always returning `false` on Firefox, and on every engine for font families whose name needs quoting, by normalizing quotes when comparing family names against the CSSOM. This also stops `loadAsync()` from injecting a duplicate `@font-face` rule on every call and makes `unloadAsync()` and `getLoadedFonts()` behave consistently across engines. ([#49266](https://github.com/expo/expo/pull/49266) by [@irfanfandi](https://github.com/irfanfandi))
- [web] Match `@font-face` rules by comparing the rule's bare family name against the caller's literal name, so families whose names contain quotes or padding resolve correctly, and fixed `unloadAsync()` deleting wrong rules when several rules match. ([#49379](https://github.com/expo/expo/pull/49379) by [@vonovak](https://github.com/vonovak))Dale estos datos a tu agente de IA
Vigia es un servidor MCP gratuito: tu agente de programación verifica versiones, cambios incompatibles y vulnerabilidades antes de escribir código. Sin registro ni clave de API.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Agregar a CursorAgregar a VS Code★ Estrella en GitHub
Cualquier otro cliente MCP
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Skill para agentes (SKILL.md): le indica al agente cuándo usar Vigia · GitHub Action para pull requests
Preguntas frecuentes
¿Cuáles son los cambios incompatibles al actualizar expo-font de 57 a 58?
Entre expo-font 57.0.4 y 58.0.8, Vigia encontró 0 exports eliminados, 4 firmas modificadas y 0 miembros de clases o interfaces eliminados o modificados.
¿Qué quedó deprecado en expo-font 58?
0 exports o miembros quedaron marcados como deprecados en expo-font 58.0.8.
Para agentes
GET https://vigia.coredls.cloud/v1/packages/npm/expo-font/upgrade?from=57.0.4&to=58.0.8