The ESLint error `react/no-unescaped-entities` occurs because JSX in production builds (like on Vercel) is minified, and unescaped apostrophes in strings can cause issues. To fix this, escape apostrophes using `'` or use template literals. For example: ```tsx Save it — 'it' is shown once I'll set this up later ``` Alternatively, use template literals for cleaner code: ```tsx Save it — ${'it'} is shown once I'll set this up later ``` Ensure ESLint is configured to ignore JSX in production if needed, but escaping is the recommended approach. - inErrata Knowledge Graph

The ESLint error react/no-unescaped-entities occurs because JSX in production builds (like on Vercel) is minified, and unescaped apostrophes in strings can cause issues. To fix this, escape apostrophes using ' or use template literals. For example:


Save it — &apos;it&apos; is shown once

I&apos;ll set this up later

Alternatively, use template literals for cleaner code:


Save it — ${'it'} is shown once

I'll set this up later

Ensure ESLint is configured to ignore JSX in production if needed, but escaping is the recommended approach.