ESLint plugin to highlight code patterns in React applications which can lead to browser exceptions while the Google Translate browser extension is in use.
npm install eslint-plugin-react-google-translateESLint plugin to highlight code patterns in React applications which can lead to browser exceptions while the Google Translate browser extension is in use. This is a common problem for React applications and a known issue to both React and Google.
When active on a page, the Google Translate browser extension is very liberal with its DOM manipulation, notably, replacing text nodes with font tags. This can be a problem for React applications as it can cause exceptions to be thrown when _conditionally_ rendering text nodes with siblings within JSX expressions.
Whilst many proposals have been suggested to avoid browser issues, this ESLint plugin aims to solve the problem far earlier in the development process by highlighting certain code patterns to the developer which can cause a browser exception to be thrown where Google Translate is in use.
Examples of code that can throw:
`` {val ? 'foo' : 'bar'} hello world {val || 'bar'} {val ? 'foo' : 'bar'} hello world {val ? foo : bar}jsx`
function SomeComponent({ val }) {
return (
// ❌ foo & bar must be wrapped
{val ? 'foo' : 'bar'} hello world
// ❌ static text nodes must be wrapped when they are preceded by a
conditional expression
{val ? foo : bar} hello world
// ❌ all text must be wrapped in spans ('foo', 'bar' & 'hello world')
// ❌ val.toLocaleString() returns a text node and should be wrapped
{val ? val.toLocaleString() : bar} hello world
// ❌ object properties rendering a text node should be wrapped
{val ? obj.a : bar} hello
// ❌ 'foo' needs to be wrapped in a span (expression has a sibling)
{val && 'foo'}
hello world
// ✅ conditionally rendered text nodes with no siblings won't throw
// ✅ conditionally rendered text nodes with no siblings won't throw
// ✅ conditional expression follows the static text node and won't throw
);
}
The safe way to write this code, avoiding browser exceptions, is to wrap each of the conditionally rendered text nodes (with siblings) in an element (for example, a ). Static text nodes with preceding conditionally rendered siblings must also be wrapped:
` {val || 'bar'} {val ? 'foo' : 'bar'}jsx`
function SomeComponent({ val }) {
return (
// ✅ all text nodes are wrapped
{val ? foo : bar}
hello world
// ✅ val.toLocaleString() is wrapped
{val ? {val.toLocaleString()} : bar}
hello world
// ✅ object properties rendering a text node are wrapped
{val ? {obj.a} : bar} hello
// ✅ 'foo' is wrapped (expression has a sibling)
{val && foo} hello world
// ✅ conditionally rendered text, but no siblings
// ✅ conditionally rendered text, but no siblings
);
}
An additional problem identified is React components returning text nodes directly (or numerical values which will be rendered as text). When a React component returns values other than JSX / null, Google Translate can continue to display stale values after state changes, without any error being thrown. Since this is very hard to debug it is better to avoid it altogether.
`tsx
export function SomeComponent({ input }) {
if (!input) {
return null; // ✅ not a problem
}
if (input === 'a') {
return 'A'; // ❌ the browser can display the stale value when state changes
} else if (input === 'b') {
return 2; // ❌ numerical values which are rendered as strings can also experience this
} else if (input === 'c') {
return Template Litera${1}; // ❌ template literals are displayed as strings and can also experience this`
} else {
return I am fine; // ✅ returning JSX prevents the problem
}
}
You'll first need to install ESLint:
`sh`
npm i eslint --save-dev
Next, install eslint-plugin-react-google-translate:
`sh`
npm install eslint-plugin-react-google-translate --save-dev
Add react-google-translate to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:
`json`
{
"plugins": ["react-google-translate"]
}
Then configure the rules under the rules section. They have been separated to allow the user to chose which rules to adopt.
`json`
{
"rules": {
"react-google-translate/no-conditional-text-nodes-with-siblings": "error",
"react-google-translate/no-return-text-nodes": "error"
}
}
Each rule can also be treated as a warning if an error is deemed too strict.
`json`
{
"rules": {
"react-google-translate/no-conditional-text-nodes-with-siblings": "error",
"react-google-translate/no-return-text-nodes": "warn"
}
}
- This plugin will highlight instances where a text node is generated by calling toString, toLocaleString, formatMessage (from react-intl) and t (from react-i18next), though it is not able to identify text nodes returned from other functions. For example, the following code will not show an error.
`jsx`
{val ? getSomeValue() : bar} hello world
- Conditional expressions are limited to a single ternary operator. Values derived from nested ternary expressions will not be reported.
- Object properties are identified by the plugin, though only those which are one level deep.
`jsxval.a
// ✅ is only one level deep and will be reportedval.a.b
{showVal ? val.a : bar} hello world
// ❌ is two levels deep and will not be reported
{showVal ? val.a.b : bar} hello world
- Optional chaining is not supported.
jsx
// ❌
val?.a uses optional chaining and will not be reported
{showVal ? val?.a : bar} hello world
// ❌ toLocaleString being optionally chained will also fail to report
{showVal ? val?.toLocaleString() : bar} hello world
`- When rendering the