sindresorhus/eslint-plugin-unicorn

Rule proposal: opposite of `prefer-string-raw`

Open

#2,652 opened on May 11, 2025

View on GitHub
 (1 comment) (2 reactions) (0 assignees)JavaScript (5,022 stars) (468 forks)user submission
help wantednew rule

Description

Description

During refactoring, some strings may not need String.raw anymore, should use a string literal instead.

Examples

// ❌
String.raw`a`

// ✅
'a'

Proposed rule name

no-string-raw

Additional Info

Not sure if we want to add a separate rule, or just add to prefer-string-raw.

Contributor guide

Tech stack
javascriptnodejs
Domain
tooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ESLint plugin developmentAST concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
This issue proposes a new rule 'no string raw' to disallow unnecessary use of String.raw. The maintainer suggested possibly extending the existing 'prefer string raw' rule. A contributor should investigate the current implementation of 'prefer string raw' in the repository to see if it can be easily extended or if a new rule is preferred. The contributor should open a discussion or draft PR to clarify the scope. The relevant files are likely in the rules/ directory of the eslint plugin unicorn repo.