npmpackage.info

Gathering detailed insights and metrics for ember-try

Other packages similar to ember-try

ember-try-config

4.0.0

Configuration generator for ember-try

ember-addon-try

0.0.11

The default blueprint for ember-cli addons.

ember-try-test-suite-helper

1.0.1

A package for use in ember-try's test suite

ember-task-scheduler

3.0.1

An Ember CLI addon to schedule tasks to try to preserve 60 FPS rate on browsers.

Gathering detailed insights and metrics for ember-try

ember-try - 4.0.0 | npmpackage.info

ember-try

An ember-cli addon to test against multiple npm dependencies, such as ember and ember-data.

4.0.0

181

MIT

JavaScript

100.73 kB

4.1

Installations

npm install ember-try

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

>= 18

Node Version

18.20.7

NPM Version

10.8.2 Pull Requests

Open

19

Total

987

Closed

590

Merged

378

Issues

Open

30

Total

121

Closed

91

Releases

v4.0.0-ember-try

Updated on Mar 07, 2025

Release 3.0.0

v3.0.0

Updated on Aug 16, 2023

Release 3.0.0-beta.1

v3.0.0-beta.1

Updated on Mar 01, 2023

Release 2.0.0

v2.0.0

Updated on Nov 04, 2021

Release 1.4.0

v1.4.0

Updated on Dec 11, 2019

Release 1.3.0

v1.3.0

Updated on Nov 11, 2019

View All 6 releases

Languages

JavaScript

HTML

Shell

Handlebars

JavaScript (98.67%)

HTML (1.2%)

Shell (0.08%)

Handlebars (0.05%)

Developer

ember-cli

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

181 Stars

870 Commits

59 Forks

10 Watchers

25 Branches

49 Contributors

Updated on Mar 07, 2025

Maintainers

View All 49 Contributors

Package Meta Information

Latest Version

4.0.0

Package Id

ember-try@4.0.0

Unpacked Size

100.73 kB

Size

23.33 kB

File Count

NPM Version

10.8.2

Node Version

18.20.7

Published on

Mar 07, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

ember-try

An ember-cli addon to test against multiple dependencies, such as ember and ember-data.

Installation

ember install ember-try

Usage

This addon provides a few commands:

`ember try:each`

This command will run ember test or the configured command with each scenario's specified in the config and exit appropriately.

This command is especially useful to use on CI to test against multiple ember versions.

In order to use an alternate config path or to group various scenarios together in a single try:each run, you can use the --config-path option.

  ember try:each --config-path="config/legacy-scenarios.js"

If you need to know the scenario that is being run (i.e. to customize a test output file name) you can use the EMBER_TRY_CURRENT_SCENARIO environment variable.

`ember try:one <scenario> (...options) --- <command (Default: ember test)>`

This command will run any ember-cli command with the specified scenario. The command will default to ember test, if no command is specified on the command-line or in configuration.

For example:

  ember try:one ember-beta --- ember test --reporter xunit

  ember try:one ember-beta --- ember serve

When running in a CI environment where changes are discarded you can skip resetting your environment back to its original state by specifying --skip-cleanup=true as an option to ember try. Warning: If you use this option and, without cleaning up, build and deploy as the result of a passing test suite, it will build with the last set of dependencies ember try was run with.

  ember try:one ember-beta --skip-cleanup=true --- ember test

In order to use an alternate config path or to group various scenarios, you can use the --config-path option.

  ember try:one ember-beta --config-path="config/legacy-scenarios.js"

`ember try:reset`

This command restores all original files, and installs the original node modules again. For use if any of the other commands fail to clean up after (they run this by default on completion) or after running with ‘—skip-cleanup’.

`ember try:ember <semver-string>`

Runs ember test or the command in config for each version of Ember that is possible under the semver string given. Configuration follows the rules given under the versionCompatibility heading below.

`ember try:config`

Displays the configuration that will be used. Also takes an optional --config-path.

Config

versionCompatibility

If you're using ember-try with an Ember addon, there is a short cut to test many Ember versions. In your package.json under the ember-addon key, add the following:

1  "ember-addon": {
2    "versionCompatibility": {
3       "ember": ">2.18.0 < 4.0.0"
4    }
5  }

The value for "ember" can be any valid semver statement. This will autogenerate scenarios for each version of Ember that matches the statement. It will also include scenarios for beta and canary channels of Ember that will be allowed to fail. These scenarios will ONLY be used if scenarios is NOT a key in the configuration file being used. If useVersionCompatibility is set to true in the config file, the autogenerated scenarios will deep merge with any scenarios in the config file. For example, you could override just the allowedToFail property of the ember-beta scenario.

To keep this from getting out of hand, ember-try will limit the versions of Ember used to the lasted point release per minor version. For example, ">1.11.0 <=2.0.0", would (as of writing) run with versions ['1.11.4', '1.12.2', '1.13.13', '2.0.0'].

Configuration Files

Configuration will be read from a file in your ember app in config/ember-try.js. Here are the possible options:

1const getChannelURL = require('ember-source-channel-url');
2
3module.exports = async function() {
4  return {
5    /*
6      `command` - a single command that, if set, will be the default command used by `ember-try`.
7      P.S. The command doesn't need to be an `ember <something>` command, they can be anything.
8      Keep in mind that this config file is JavaScript, so you can code in here to determine the command.
9    */
10    command: 'ember test --reporter xunit',
11    /*
12      `npmOptions` - options to be passed to `npm`.
13    */
14    npmOptions: ['--loglevel=silent'],
15    /*
16      If set to true, the `versionCompatibility` key under `ember-addon` in `package.json` will be used to
17      automatically generate scenarios that will deep merge with any in this configuration file.
18    */
19    useVersionCompatibility: true,
20    /*
21      The package manager to use for all scenarios. By default, lockfiles will be ignored when installing dependencies.
22      At cleanup, all dependencies will be restored to their prior state.
23    */
24    packageManager: 'npm' | 'pnpm' | 'yarn',
25
26    /*
27      buildManagerOptions allows you to opt-out of the default options such as `--ignore-engines --no-lockfile`.
28      The buildManagerOptions function is aware of each scenario so you can customize your options.
29    */
30    buildManagerOptions(scenario) {
31      return ['--ignore-engines'];
32    }
33
34    scenarios: [
35      {
36        name: 'Ember 2.11.0',
37        /*
38          `env` can be set per scenario, with environment variables to set for the command being run.
39          This will be merged with process.env
40       */
41        env: {
42          ENABLE_NEW_DASHBOARD: true
43        },
44        npm: {
45          devDependencies: {
46            'ember-source': '2.11.0'
47          },
48          /*
49            You can optionally define npm or pnpm overrides to enforce a specific dependency version
50            to be installed. This is useful if other libraries you depend on include different
51            versions of a package. This does nothing if `packageManager` is `yarn`;
52          */
53          overrides: {
54            'lodash': '5.0.0'
55          }
56          /*
57            When `packageManager` is `yarn`, you can optionally define yarn resolutions to enforce a
58            specific dependency version to be installed. This is useful if other libraries
59            you depend on include different versions of a package.
60          */
61          resolutions: {
62            'lodash': '5.0.0'
63          }
64          /*
65            In order to easily test multiple editions ember-try merges any `ember` property specified
66            into the applications `package.json`. Values specified in the ember-try configuration will
67            override values that pre-existed in the original `package.json`.
68          */
69          ember: {
70            'edition': 'octane'
71          }
72        }
73      },
74      {
75        name: 'Ember canary with Ember-Data 2.3.0',
76        /*
77          `allowedToFail` - If true, if this scenario fails it will not fail the entire try command.
78        */
79        allowedToFail: true,
80        npm: {
81          devDependencies: {
82            'ember-data': '2.3.0',
83
84            'ember-source': await getChannelURL('canary')
85
86            // you can remove any package by marking `null`
87            'some-optional-package': null
88          }
89        },
90      },
91      {
92        name: 'ember-beta',
93        npm: {
94          devDependencies: {
95            'ember-source': await getChannelURL('beta')
96          }
97        }
98      },
99    ]
100  };
101};

Scenarios are sets of dependencies. They can be specified exactly as in the package.json The name can be used to try just one scenario using the ember try:one command.

Yarn

If you include packageManager: 'yarn' in your ember-try config, all npm scenarios will use yarn for install with the --no-lockfile option. At cleanup, your dependencies will be restored to their prior state.

Pnpm

If you include packageManager: 'pnpm' in your ember-try config, all npm scenarios will use pnpm for install with the --no-lockfile options. At cleanup, your dependencies will be restored to their prior state.

⚠ pnpm versions from 8.0.0 to 8.6.x have the default value of resolution-mode setting changed to lowest-direct. This violates ember-try expectations as resolution-mode is expected to be highest, like in npm and pnpm versions < 8.0.0 and >= 8.7.0.

If you run into this issue, we recommend to upgrade pnpm to latest version. If you are unable to upgrade, you can set resolution-mode = highest in the .npmrc file.

A note on npm scenarios with lockfiles

Lockfiles are ignored by ember-try. (yarn will run with --no-lockfile and npm will be run with --no-package-lock and pnpm will be run with --no-lockfile). When testing various scenarios, it's important to "float" dependencies so that the scenarios are run with the latest satisfying versions of dependencies a user of the project would get.

Workspaces

If you include useWorkspaces: true in your ember-try config, ember-try will apply the diff to each individual workspace specified in package.json, allowing you to try scenarios in monorepo style repositories. See Yarn's documentation of workspaces for more details.

Video

See an example of using ember-try for CI here, and the resulting build output.

Special Thanks

Much credit is due to Edward Faulkner The scripts in liquid-fire that test against multiple ember versions were the inspiration for this project.

Developing

Be sure to run npm link and npm link ember-try, otherwise any ember try commands you run will use the version of ember-try included by ember-cli itself.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

9

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:209: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:210: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:211: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:234: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:235: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:236: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:61: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:62: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:63: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:146: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:147: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:148: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:179: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:180: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:181: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/ci.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/plan-release.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/plan-release.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/plan-release.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/plan-release.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/plan-release.yml:56: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/plan-release.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/publish.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/publish.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/ember-cli/ember-try/publish.yml/main?enable=pin
Warn: npmCommand not pinned by hash: .github/workflows/ci.yml:190
Warn: npmCommand not pinned by hash: .github/workflows/ci.yml:160
Info: 0 out of 16 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 12 third-party GitHubAction dependencies pinned
Info: 0 out of 2 npmCommand dependencies pinned

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Reason

45 existing vulnerabilities detected

Details

Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
Warn: Project is vulnerable to: GHSA-whgm-jr23-g3j9
Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
Warn: Project is vulnerable to: GHSA-fwr7-v2mv-hh25
Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
Warn: Project is vulnerable to: GHSA-wxhq-pm8v-cw75
Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
Warn: Project is vulnerable to: GHSA-6c8f-qphg-qjgp
Warn: Project is vulnerable to: GHSA-3rfm-jhwj-7488
Warn: Project is vulnerable to: GHSA-hhq3-ff78-jv3g
Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
Warn: Project is vulnerable to: GHSA-pc58-wgmc-hfjr
Warn: Project is vulnerable to: GHSA-vvv8-xw5f-3f88
Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
Warn: Project is vulnerable to: GHSA-76p7-773f-r4q5
Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
Warn: Project is vulnerable to: GHSA-jv35-xqg7-f92r
Warn: Project is vulnerable to: GHSA-4g88-fppr-53pp
Warn: Project is vulnerable to: GHSA-4jqc-8m5r-9rpr
Warn: Project is vulnerable to: GHSA-jgrx-mgxx-jf9v
Warn: Project is vulnerable to: GHSA-hc6q-2mpp-qw7j
Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986
Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q

Score

4.1

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to ember-try

Other packages similar to ember-try

ember-try

Installations

Developer Guide

No

CommonJS

>= 18

18.20.7

10.8.2

Pull Requests

19

987

590

378

Issues

30

121

91

Releases

Languages

Developer

ember-cli

Download Statistics

GitHub Statistics

Maintainers

Package Meta Information

Total Downloads

NaN

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

ember-try

Installation

Usage

ember try:each

ember try:one <scenario> (...options) --- <command (Default: ember test)>

ember try:reset

ember try:ember <semver-string>

ember try:config

Config

versionCompatibility

Configuration Files

Yarn

Pnpm

A note on npm scenarios with lockfiles

Workspaces

Video

Special Thanks

Developing

10

10

10

10

9

0

0

0

0

0

0

0

0

4.1

/10

`ember try:each`

`ember try:one <scenario> (...options) --- <command (Default: ember test)>`

`ember try:reset`

`ember try:ember <semver-string>`

`ember try:config`