[@rollup/plugin-replace]do not support replace chinese language

[liangxiwei]

• Rollup Plugin Name: @rollup/plugin-replace
• Rollup Plugin Version: 5.0.2
• Rollup Version: 2.75.6
• Operating System (or Browser): chrome
• Node Version: v20.0.0
• Link to reproduction (⚠️ read below):

plugins: [ replace({ values: { 左边: "xxxx", }, }), ],
App.tsx
<div>左边</div>

Expected Behavior

“左边” will be replace to "xxxx"

Actual Behavior

can not replace

Additional Information

[liangxiwei]

when call plugin transform hook,the chinese in args code is unicode,and the '左边' look like not match chinese unicode

[potatohoney-p]

There are two separate matching issues here.

With @rollup/plugin-replace@5.0.2, the default \b delimiters do not match the boundaries around 左边 in <div>左边</div>. This works on the original, unescaped text:

replace({
  preventAssignment: true,
  delimiters: ['', ''],
  values: { '左边': 'xxxx' }
})

Empty delimiters also replace substrings (左边栏 becomes xxxx栏), so restrict include or use more specific delimiters if that is not intended.

Your follow-up about escaped Unicode is a second issue: if an earlier transform has already emitted the literal source text \u5DE6\u8FB9, a key containing 左边 cannot match it. The plugin replaces source text, not decoded JavaScript string values. Run the replacement before the transform that escapes the characters, or match the exact emitted spelling, for example:

values: { [String.raw`\u5DE6\u8FB9`]: 'xxxx' }

The spelling/case of that escape must match the generated source; this is more brittle than replacing before escaping.

I checked the transform hook directly on Node 24.22.1 with plugin versions 5.0.2 and 6.0.3. Version 6.0.3 replaces the raw <div>左边</div> with its default delimiters, so that particular boundary problem is version-dependent. Both versions still require matching the actual source spelling once it is escaped. These checks isolate replacement behavior; they do not reproduce your full TSX pipeline.