You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can optionally define npm overrides to enforce a specific dependency version
152
+
You can optionally define npm or pnpm overrides to enforce a specific dependency version
148
153
to be installed. This is useful if other libraries you depend on include different
149
154
versions of a package. This does nothing if `useYarn` is true;
150
155
*/
@@ -206,9 +211,14 @@ The `name` can be used to try just one scenario using the `ember try:one` comman
206
211
207
212
If you include `useYarn: true` 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.
208
213
214
+
##### Pnpm
215
+
216
+
If you include `usePnpm: true` in your `ember-try` config, all npm scenarios will use `pnpm` for install with the `--frozen-lockfile=false` option. At cleanup, your dependencies will be restored to their prior state.
217
+
218
+
209
219
##### A note on npm scenarios with lockfiles
210
220
211
-
Lockfiles are ignored by `ember-try`. (`yarn` will run with `--no-lockfile` and `npm` will be run with `--no-shrinkwrap`).
221
+
Lockfiles are ignored by `ember-try`. (`yarn` will run with `--no-lockfile` and `npm` will be run with `--no-shrinkwrap` and `pnpm` will be run with `--frozen-lockfile=false`).
212
222
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.
0 commit comments