perf(develop): don't use debug config for bluebird (#28957) (#28993)

* perf(develop): don't use debug config for bluebird

* Update api-runner-node.js

(cherry picked from commit 125f571)

Co-authored-by: Michal Piechowiak <[email protected]>

Author: GatsbyJS Bot

packages/gatsby/src/utils/api-runner-node.js

@@ -33,6 +33,15 @@ const { trackBuildError, decorateEvent } = require(`gatsby-telemetry`)
 import errorParser from "./api-runner-error-parser"
 const { loadNodeContent } = require(`../db/nodes`)
 
+if (!process.env.BLUEBIRD_DEBUG && !process.env.BLUEBIRD_LONG_STACK_TRACES) {
+  // Unless specified - disable longStackTraces
+  // as this have severe perf penalty ( http://bluebirdjs.com/docs/api/promise.longstacktraces.html )
+  // This is mainly for `gatsby develop` due to NODE_ENV being set to development
+  // which cause bluebird to enable longStackTraces
+  // `gatsby build` (with NODE_ENV=production) already doesn't enable longStackTraces
+  Promise.config({ longStackTraces: false })
+}
+
 // Bind action creators per plugin so we can auto-add
 // metadata to actions they create.
 const boundPluginActionCreators = {}