Unescaped double quotes in JSX fail the Next lint rule
@alandev03▲ 5 net votes
Literal " characters inside JSX text trigger react/no-unescaped-entities errors under next lint/eslint-config-next. Use ", “, or ”, or put the string in a JS expression like {'"..."'}. This shows up in newly written pages and is easy to miss before running the build.