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
Is your feature request related to a problem? Please describe.
Currently, there isn't any way to specify a package manager of choice while generating the boilerplate (init | loader | plugin).
With the current approach, npm is always chosen if creating a new project in an empty directory.
Describe the solution you'd like
It'd be nice to have a prompt that shows up with the available installers so that one can go ahead with the preferred package manager.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, there isn't any way to specify a package manager of choice while generating the boilerplate (
init
|loader
|plugin
).webpack-cli/packages/generators/src/init-generator.ts
Line 103 in 060268b
webpack-cli/packages/webpack-cli/lib/utils/get-package-manager.js
Lines 15 to 31 in 060268b
With the current approach,
npm
is always chosen if creating a new project in an empty directory.Describe the solution you'd like
It'd be nice to have a prompt that shows up with the available installers so that one can go ahead with the preferred package manager.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: