how to disable ignored-builds feature

[babakfp]

How can I just disable it for all projects at once, like in a global config file...

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

[zkochan]

There is no setting to disable it globally. To disable it for a project, you can add this to pnpm-workspace.yaml:

neverBuiltDependencies: []

[zkochan]

pnpm v10.9 now has an option to allow all builds: dangerouslyAllowAllBuilds

it should be set in pnpm-workspace.yaml.

[lash0000]

So if I wanted to allow it, I am expecting to worry about dependencies especially for new version ones but it looks stable anyway?

[Exagram]

Issue: this "feature" breaks create-next-app.

Unfortunately pnpm-workspace.yaml is created after create-next-app so it doesn't override this annoyance.

How can I globally disable it by default?

It is Security Theatre that adds the appearance of security but in actuality it trains developers' muscle memory to blindly pnpm approve-build on every build which adds little to no security at all!

[kadvehcp]

ok here is a thing when i run create next-app@latest it block two scripts sharp and unrs-resolver. and gives an error which looks bad it shouldn't be there since i am developing on my own computer there has to be a way or anything to stop blocking those scripts with global config file or a flag or something like that. i don't want to run a seperate command like pnpm approve-builds it is frustrating. when i create that workspace yaml file and allow them there then create next-app give error that file exist there can't do it. so please provide an option to stop blocking things and let everything happen smoothly. i don't want to create that file just to allow some basic things. just like npm has this thing which does exactly this npm config set dangerously-allow-all-scripts true --location=user