`fast-png` dependency creates a `latin1` TextDecoder at import-time, crashing runtimes that don't contain `latin1` support

[cn1001wang]

Environment

• roslib version: 2.x (latest)
• Platform: React Native (Expo Bare)
• JS engine: Hermes
• OS: Android (also reproducible on iOS with Hermes)
• Transport: rosbridge WebSocket

Description

After upgrading from roslib 1.4.1 to 2.x, the app crashes at startup in a React Native environment using Hermes. The error appears to originate from dependencies (likely BSON / Buffer usage) that rely on encodings unsupported by Hermes.

Error Logs

WARN  BSON: For React Native please polyfill crypto.getRandomValues
ERROR RangeError: Unknown encoding: latin1 (normalized: latin1), js engine: hermes

Steps to Reproduce

1. Create a React Native project (Expo Bare or CLI).
2. Enable Hermes (default in recent RN versions).
3. Install roslib 2.x:

npm install roslib

4. Import and create a Ros instance:

import { Ros } from 'roslib'

const ros = new Ros({
  url: 'ws://localhost:9090'
})

5. Run on Android or iOS.

Expected Behavior

roslib should initialize normally in React Native, or documentation should clarify that RN is not supported.

Actual Behavior

Application crashes with:

RangeError: Unknown encoding: latin1

Questions

1. Is React Native (Hermes) officially supported in roslib v2?
2. Are there recommended polyfills or configuration steps to make v2 work in RN?
3. If RN is not supported, would it be possible to document this limitation?
4. Is there any plan to provide a RN-compatible build (without Node-specific encoding dependencies)?

Thank you!

[MatthijsBurgh]

I don't think we support any frameworks like react. They work or not. We are open to fixes that extend compatibility.

@EzraBrooks do you have any tips to get it working?

[EzraBrooks]

I think we certainly should support React, etc. since it's how most people write JS apps.

This seems like a bug internal to bson, unfortunately. Are you actually using BSON on your rosbridge, or is roslibjs erroneously attempting to do BSON things where it's not needed?

[EzraBrooks]

Actually, this line in fast-png appears to be the culprit:

https://github.com/image-js/fast-png/blob/77a4479d68d84246793f58f7bbf2a2ea3a80c0f5/src/helpers/text.ts#L11

A globally-scoped TextDecoder that is constructed at import time.

I think perhaps roslibjs can lazy-load PNG support.