Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

`ng update @angular/fire` stops before the v21 migration when it runs Angular CLI 22.3

Cerrado
  • ¿Algo no está bien?
#3,789 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Ya se ha fusionado un pull request relacionado.

  • #3793 de @armando-navarro — fusionado

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
angular, firebase, typescript
Área
developer-experience, tooling

Línea de trabajo

Read the three affected bundles named in the issue: setup/index.js, deploy/builder.js, and update/v21/index.js. Compare their @angular-devkit/schematics/tasks/index.js usage with the 22.3.0-next.0 exports map. Done means ng update @angular/fire --next can load the v21 migration and complete without ERR_PACKAGE_PATH_NOT_EXPORTED; note that linked pull request #3793 is already open.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

comp: schematics type: bug version: current (v17+)

In an Angular 21 app, ng update @angular/fire --next installs 21.0.0-rc.1 and then stops with an error, so the v21 migration never runs. That migration is what moves the app's firebase dependency to ^12, among other changes.

Installing a temporary Angular CLI versioned next to perform the update.
...
Updating package.json with dependency @angular/fire to version 21.0.0-rc.1...
An unhandled exception occurred: Package subpath './tasks/index.js' is not defined by "exports" in .../node_modules/@angular-devkit/schematics/package.json
Details
  • ng update without a version on the Angular packages runs a temporary copy of the newest Angular CLI. With --next that is 22.3.0-next.0 today.
  • @angular-devkit/schematics 22.3.0-next.0 adds an exports map that lists ./tasks but not ./tasks/index.js. 22.2.1 and 21.2.25 have no exports map.
  • Three of AngularFire's schematic bundles require @angular-devkit/schematics/tasks/index.js: setup/index.js, deploy/builder.js and update/v21/index.js. Loaded with 22.3.0-next.0, each fails with ERR_PACKAGE_PATH_NOT_EXPORTED.
  • Angular CLI's own ng update --next listing suggests running ng update @angular/fire --next.
  • Plain ng update @angular/fire also runs the newest CLI, so it will fail the same way once Angular CLI 22.3 is published as latest.
Workaround

Name the version, for example ng update @angular/[email protected]. That form runs the project's own Angular CLI, and the migration runs.

Lenguaje dominante
TypeScript
Estrellas
7.8k
Forks
2.2k
Merge medio
2 d 14 h
PR fusionados (30 d)
19

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de angular/angularfire

Todos los issues de angular/angularfire

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.