UnhandledPromiseRejectionWarning on first deploy

[ikoruk]

When running clone+deploy, I get weird message about my Web Pages not including a locale (which I don't see any way of changing on the admin interface). And then there is an UnhandledPromiseRejectionWarning with a TypeError which causes the deploy to fail.

[okbel]

Hi @ikoruk !

Could you retry it and let us know? We had some issues last week with @bigcommerce API and I'd like to check if those are related or not.

Thank you!

[RayeEThompson]

👋 @ikoruk, I'm @RayeEThompson a Developer Advocate at BigCommerce. I would love to know if this is still occurring. If it is, I can help you update any products locale via REST API call.

[ikoruk]

It does seem to be different now, but I get the error Type error: File '/vercel/workpath0/hooks/useCart.ts' is not a module. on a fresh install.`

Edit: This seems to be an unrelated issue from today. When I build locally on an older commit, I get the following (which seems to be unrelated to locale):

info  - Compiled successfully
info  - Collecting page data .(node:67482) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    --- property 'issuerCertificate' closes the circle
    at stringify (<anonymous>)
    at writeChannelMessage (internal/child_process/serialization.js:117:20)
    at process.target._send (internal/child_process.js:804:17)
    at process.target.send (internal/child_process.js:702:19)
    at reportError (/Users/yschwart/Developer/commerce/node_modules/jest-worker/build/workers/processChild.js:103:11)
    at reportClientError (/Users/yschwart/Developer/commerce/node_modules/jest-worker/build/workers/processChild.js:87:10)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:67482) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:67482) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.```

[okbel]

Looks like this has been fixed a long time ago.