ember-cli / ember-cli/ember-try
Ember beta or Ember Data beta don’t get properly installed after e12c4ca
- Langage dominant
- JavaScript
- Étoiles
- 180
- Forks
- 57
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hey, this is extracted from #207, which I thought was the same problem but [isn’t](https://github.com/ember-cli/ember-try/issues/207#issuecomment-448882870)!
As @kategengler suggested, when I [tried](https://github.com/ember-cli/ember-try/issues/207#issuecomment-449055834) installing e12c4ca, it worked as expected with the `travis-web` [`ember-try` configuration](https://github.com/travis-ci/travis-web/blob/889fb9db2e1ed5b7e48c3c4e20fafae3ece207df/config/ember-try.js) of `'ember-source': 'beta'` and `'ember-data': 'beta'`. After that commit, `ember try:one ember-data` fails because the `ember-source` package isn’t installed.
You can see an example of such a failure [here](https://travis-ci.org/travis-ci/travis-web/jobs/433639308#L606-L609).
Let me know if there’s any other information I can provide. Thanks for all the work on this, I appreciate the automation so we can try to find issues with the betas early!
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by reproducing `ember try:one ember-data` with the linked travis-web `config/ember-try.js` configuration and compare the behavior before and after commit e12c4ca. Confirm the beta setup installs both `ember-data` and `ember-source`; done means the command no longer omits `ember-source`.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript, node.js
- Domaine
- testing
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100