Custom error returns and production environment

[ghost]

Question

What I'm seeing is that when I'm in the dev or staging node environment, my custom error strings that are returned from the rule are correct and all my tests (Jest unit and integration) pass that are expecting the specific custom error message that should get returned from the rule if it fails. But when I deploy to production and the node environment is now production, the fallback error message is displayed for the same scenario. Does graphql-shield have a production environment over ride, I don't see anything in the docs or github issues specifying this?

Background

currrently using graphql-shield v. 7.4.2

permissions options being used/set:
{ debug: process.env.NODE_ENV !== 'production', allowExternalErrors: true, fallbackError: new Error(FALLBACK_ERROR), }

[ghost]

Update/Answer

production ended up not factoring into my question or issue. A utility function I was using in my rule was throwing an error without it being handled. With debug false in production the fallback error message was being used because of the error being thrown and not returned by the rule itself.