Unable to deploy on windows using ng deploy
- Langage dominant
- TypeScript
- Étoiles
- 7.8k
- Forks
- 2.2k
- Merge moyen
- 22 h 28 min
- PR mergées (30 j)
- 6
Description
### Version info
**Angular:** 13.3.0
**Firebase:** 9.6.10
**AngularFire:** 7.2.1
**Node:** 16.13.2
**Operating System:** Windows 11
### How to reproduce these conditions
**Unable to deploy on windows using ng deploy**
Hi, when I am trying to deploy the my app which have SSR enabled for firebase functions using ng deploy it just doesn't work.
Deployment just fails with error message : `Your code contains errors while deploying function ssr_app`
After many hours of searching I found that it is creating wrong package.json file it has a dependency stating myprojectname with value file:../../.. which looks like this exactly `"my-project": "file:../../.."`
This error is only being produced on windows machine, same doesn't happen on mac. Also manually removing that line and running firebase deploy does the job.
### Debug output
** Errors in the JavaScript console **
** Output from `firebase.database().enableLogging(true);` **
** Screenshots **

### Expected behavior
It should generate package.json correctly and invalid dependency should not be added in it.
### Actual behavior
It is adding an invalid dependency in generated function directory's package.json file which looks like this `"my-project": "file:../../.."`
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Reproduisez ng deploy sous Windows 11 avec une application Firebase functions utilisant SSR, en employant les versions indiquées dans l’issue. Examinez le package.json du répertoire de fonctions généré et comparez-le au déploiement sous macOS. La tâche est terminée lorsque la dépendance invalide file:../../.. n’est pas générée et que le déploiement réussit sans modifier manuellement package.json.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, firebase, typescript
- Domaine
- cloud, devops
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100