Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

Continuing from Issue 9102

Having a flag like --allow-all-builds makes sense. Consider the following command to create a nuxt project -

npm create nuxt@latest

It first creates the project folder, and then asks which package manager do I want to use to install the dependencies. @parcel/watcher, and esbuild scripts are not allowed, and hence ignored. Since, I don't even have the package.json yet, I can't put anything to it which will allow the builds.

I can't run the command npm create nuxt@latest again, because then it will be a new nuxt project. I can't even use pnpm approve-builds, because now it doesn't show any ignored approve-builds. Only option left for me is to use npm package manager, which defeats the purpose having pnpm.

D:\Projects>npm create nuxt@latest

> npx
> create-nuxt

√ Which package manager would you like to use?
pnpm

o Installing dependencies...

╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮
│                                                                                            │
│   Ignored build scripts: @parcel/watcher, esbuild.                                         │
│   Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.   │
│                                                                                            │
╰────────────────────────────────────────────────────────────────────────────────────────────╯

Done in 17.2s using pnpm v10.18.3

Describe the solution you'd like

Have --allow-all-builds for allowing all the builds while running the commands which can't be run otherwise again on the same thing

Describe the drawbacks of your solution

No response

Describe alternatives you've considered

No response