ember-try
ember-try copied to clipboard
ember-cli
An ember-cli addon to test against multiple npm dependencies, such as ember and ember-data.
Maybe extract a util package from ember-cli? If so, also use for the determination of yarn pnp (#214)
If I interrupt or kill `ember try:each`, it seems to throw my application into disarray with a number of different errors: ``` Unexpected end of JSON input at JSON.parse ()...
Running into this with the [ember-decorators](https://travis-ci.org/ember-decorators/ember-decorators/) library. Currently, the library is set up as a monorepo that consists of many addon packages, managed by `lerna`. This setup works well, but...
Is there a way to use `versionCompatibility` with `ember try:each` and have the jobs run parallel on Travis? Mirage's current `.travis.yml` looks like [this](https://github.com/samselikoff/ember-cli-mirage/blob/master/.travis.yml#L44-L60) and I'm wondering if there's a...
When running a single scenario such as: ``` ember try:one ember-canary --- ember s --port=0 ``` When you close the server (via `ctrl-c` generally), the following error is emitted: ```...
After https://github.com/ember-cli/ember-cli/pull/7536 most addons will use ember-try with urls for tarballs for release/beta/canary. As is seen in the output in the comments on that PR, the URL is truncated to...
Quick enhancement suggestion: A parameter for indicating that one would like an ember-try process to cleanup/exit immediately after failing a non-allowedToFail scenario.
Once https://github.com/ember-cli/ember-try-config/issues/13 is implemented we should deprecate the usage of the `useVersionCompatibility` flag and instead explicitly import and use the scenario generator as detailed in the issue above.
## Own files that may be mistakenly published: - all-commands - lint-test.js - tests - upload-coverage.sh ## dependencies that may need to be investigated (830): - [ ] cli-table2 532...
Getting the following error: ``` Assertion Failed: The template being rendered by `` was compiled with `[email protected]` which does not match `[email protected]` (this revision). ``` 1.11 scenario passes, then all...
