Feature parity review: untracked DevUtils-style tools

What feature or new tool do you think should be added to DevToys?

While reviewing DevToys alongside DevUtils for feature parity, I found a small set of local developer utilities for which I couldn't find an exact current issue or PR, or a previous decision rejecting the capability for built-in inclusion.

Area	Candidate capability	Minimal behavior
Formatting	ERB beautify/minify	Format or minify ERB while preserving template expressions.
Formatting	LESS and SCSS beautify/minify	Format or minify each stylesheet syntax without converting it to another language.
Conversion	HTML → JSX	Convert HTML attributes and inline styles to valid JSX equivalents.
Conversion	PHP value/array source → JSON	Parse common PHP array/value syntax into JSON without executing arbitrary PHP code. This is distinct from PHP serialized-data conversion.
Conversion	SVG → CSS	Produce a CSS background-image value using URL-encoded or Base64-encoded SVG data.
Identifiers	ULID generate/decode	Generate ULIDs and decode their timestamp and randomness components.
Identifiers	UUID decode/inspect	Show version, variant, and version-specific fields such as timestamps or node data where applicable.

Why do you think this is needed?

These are common "paste, inspect or transform, copy" tasks. Without a local tool, they often require a one-off dependency, custom script, or browser service that may receive proprietary source or data.

Solution/Idea

The formatter tools could use an explicit Beautify/Minify selector. The conversion tools could use DevToys' existing input/output pattern. PHP conversion shouldn't execute input.

The identifier tool could generate ULIDs, decode ULID timestamps and randomness, and inspect UUID version, variant, and version-specific fields.

Comments

I searched the existing DevToys issue and PR history before drafting this. Some nearby issues weren't treated as duplicates:

• #197 requested conversion among CSS, Less, Sass, and SCSS; it didn't request beautifying or minifying those syntaxes.
• #424 concerned PHP serialized data; the PHP→JSON candidate above concerns ordinary PHP value/array source.
• #1238 added UUID v7 generation; it didn't cover ULIDs or general UUID decoding/inspection.

I also excluded capabilities that already have an active tracker and requests that were previously declined for built-in inclusion.