Bug: JSON response shows Unicode escape sequences instead of rendered characters

[rajib-raiyat]

I have checked the following:

• I have searched existing issues and found nothing related to my issue.

This bug is:

• making Bruno unusable for me
• slowing me down but I'm able to continue working
• annoying
• this feature was working in a previous version but is broken in the current release.

Bruno version

v2.14.0

Operating System

Linux Mint 21.3; Kernel: 5.15.0-160-generic

Jira

Describe the bug

After updating Bruno from version v2.13.2 to v2.14.0, the JSON response view no longer renders multi-byte characters (specifically Bengali/Bangla) correctly. Instead of displaying the actual readable text, it now shows the raw Unicode escape sequences (e.g., \u09b8\u09be...).

This appears to be a regression, as this functionality worked perfectly in v2.13.2.

---

Version Information

• Bruno Version: v2.14.0
• Previous Working Version: v2.13.2

---

Steps to Reproduce

1. Use Bruno v2.14.0.
2. Create and send a request to any API endpoint that returns a JSON response containing Bengali (or likely any non-ASCII) characters.
3. Go to the Response tab.
4. Observe the JSON body in the "Response" view.

---

Expected Behavior

The JSON response view should parse and render the Unicode sequences as readable Bengali characters, just as it did in v2.13.2.

Example of Expected View (v2.13.2):

{
  "success": true,
  "data": {
    "title": "Some readable text in Bengali", // Or any other language
    "description": "The characters are rendered correctly."
  }
}

---

Actual Behavior

The JSON response view displays the raw, un-rendered Unicode escape sequences.

Example of Actual View (v2.14.0):

{
  "success": true,
  "data": {
    "title": "\u09b8\u09be\u0987\u09a8\u09c1\u09b8\u09be...", // Raw Unicode displayed
    "description": "\u0997\u09c1\u09b0\u09c1\u099c\u09c0\u09b0..."
  }
}

.bru file to reproduce the bug

No response

Screenshots/Live demo link

[rajib-raiyat]

When I use the Filter With JSONPath feature, the JSON response shows the real characters correctly (not the Unicode escape sequences)

[helloanoop]

Hey @rajib-raiyat

Thanks for reporting this. We recently made some updates to the response rendering logic to fix issue related to bigints being rounded- PR (#6026) which has caused this regression.

We looking into this right now. You can expected a hotfix shortly.

[helloanoop]

Mad changes in our formatter to match parity with JSON.stringify() handling of unicode sequences.

v0.3.0 of the library has been released. Next step is to update bruno app to use it and get a hotfix out.

cc @bijin-bruno @lohit-bruno

[bijin-bruno]

@rajib-raiyat This issue has been fixed in Bruno v2.14.1 🎉