You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all!
I am noticing that the npm run build command doesn't always exit after successful completion of the build, which causes timeout failures while using this approach in CI. This is typically replicable locally (although it seems that it occasionally does exit) , but seems to be consistently replicable in CI.
Hi all!
I am noticing that the
npm run build
command doesn't always exit after successful completion of the build, which causes timeout failures while using this approach in CI. This is typically replicable locally (although it seems that it occasionally does exit) , but seems to be consistently replicable in CI.Any insights on what way cause this issue?
Using
[email protected]
and[email protected]
. Scripts in package.json are set up following the documentation.It seems that the builds are completing properly, but, typically, the command doesn't exit. Here's a screenshot of the terminal output:

My config override looks something like this:
The text was updated successfully, but these errors were encountered: