Skip to content

Conversation

@manud99
Copy link
Contributor

@manud99 manud99 commented Jan 14, 2026

Description

Upon a bundling error you only see a message like the following one, which I found not that helpful.

BundlingFailedError: Bundling of app/services/Network.harness.ts failed
        at construct (native)
        at apply (native)

I found that the reason field in BundleFailedError contains a nicely formatted error message. This PR makes the app print this error message in the console like this:

BundlingFailedError: Bundling of app/services/Network.harness.ts failed with error:

    Unable to resolve module @/config from ...: @/config could not be found within the project or in these directories:
      node_modules
      1 | import { Platform } from "react-native"
    > 2 | import Config from "@/config"
        |                     ^
      ...

        at construct (native)
        at apply (native)

Testing

I tested it my modifying these files locally for my project.

@vercel
Copy link

vercel bot commented Jan 14, 2026

@manud99 is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

@V3RON V3RON left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!
I was about to make the same change, but you beat me to it 😄

@V3RON V3RON merged commit 0472f00 into callstackincubator:main Jan 15, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants