Add `err` and/or `opts` to the no-param-reassign exclusions?

Hey there.

Most frequent i have problem with this rule. And specifically in cases of options, opts and err. I also seen in #1089 that this rules is disabled for different reasons. What’s your thoughts? Could you consider adding opts and err?

I know that there is a bit better and more proper way for adding to the error instance, for example creating whole new error class based on the original one. But there is simple things like adding some single metadata property.

In my case such metadata is err.commandArgv and err.commandName where commandName isn’t exactly the terminal/unix one, but command of some cli - for example mycli hello so err.commandName will be hello regardless what that command does.

[ljharb]

Do you actually need the stack trace from the original error? If not, it seems like it’d be better to make a new Error instance; either way, you can do Object.assign(err, { comandName: 'blah' }) and the linter rule won’t complain.

[tunnckoCore]

Do you actually need the stack trace from the original error?

Exposing that to third party, so it depends.

and the linter rule won’t complain.

Ahhh, sweet! How i forgot about that? 😸 Thanks.