package manager (npm, yarn, etc.) is not asked in style (How would you like to use ESLint) option

[hitesh-can-code]

Two questions (that is install the deps and what package manager) are skipped when choose to style options.

[Rec0iL99]

Hello @hitesh-can-code, could you please provide more details about what you mean by 'style options'?

[hitesh-can-code]

eslint need to ask what package manager first than checking peersdeps

[Rec0iL99]

I couldn't reproduce this on my local machine

> bun create @eslint/config                                                                                                                                                                                            
✔ How would you like to use ESLint? · style
✔ What type of modules does your project use? · esm
✔ Which framework does your project use? · none
✔ Does your project use TypeScript? · No / Yes
✔ Where does your code run? · node
✔ How would you like to define a style for your project? · guide
✔ Which style guide do you want to follow? · standard-with-typescript
✔ What format do you want your config file to be in? · JSON
Checking peerDependencies of eslint-config-standard-with-typescript@latest
The config that you've selected requires the following dependencies:

eslint-config-standard-with-typescript@latest @typescript-eslint/eslint-plugin@^6.4.0 eslint@^8.0.1 eslint-plugin-import@^2.25.2 eslint-plugin-n@^15.0.0 || ^16.0.0  eslint-plugin-promise@^6.0.0 typescript@*
✔ Would you like to install them now? · No / Yes
? Which package manager do you want to use? … 
❯ npm
  yarn
  pnpm

I'm getting the option to choose which package manager.

> bun --version                                                                                                                                                                                                        
1.0.29

Did I miss something?

[hitesh-can-code]

it is because you have npm installed where i only have bun

[aladdin-add]

it was not using npm to install any dependencies, it was to check the package's peer dependencies:

create-config/lib/init/npm-utils.js

Lines 71 to 75 in 9c4214b

	const npmProcess = spawn.sync(
	"npm",
	["show", "--json", packageName, "peerDependencies"],
	{ encoding: "utf8" }
	);

for no-npm-installed envs, we could find another way to do it.