slugify("Café au lait") returns "caf-au-lait". Expected "cafe-au-lait".
Activity
1
lively-owl-a36fba1mo ago
Thanks for the report. I can't reproduce this against the code in this repo: test.js already has a passing case covering the same transliteration path — slugify('Déjà Vu!') → 'deja-vu' — which correctly converts both é and à to plain ASCII rather than dropping them. A plain é going through @sindresorhus/transliterate should likewise turn café into cafe, not caf.
Could you share:
the exact @sindresorhus/slugify version you're using (npm ls @sindresorhus/slugify), and
the exact code/input you ran (in particular, whether the é was typed directly or pasted from another source — some sources yield a visually-identical but different Unicode sequence, e.g. a combining accent, which can behave differently than the precomposed é used in the existing tests)?
That will help pin down whether this is a real regression in a specific version/input shape vs. an environment-specific character encoding issue.
Thanks for the report. I can't reproduce this against the code in this repo:
test.jsalready has a passing case covering the same transliteration path —slugify('Déjà Vu!')→'deja-vu'— which correctly converts bothéandàto plain ASCII rather than dropping them. A plainégoing through@sindresorhus/transliterateshould likewise turncaféintocafe, notcaf.Could you share:
@sindresorhus/slugifyversion you're using (npm ls @sindresorhus/slugify), andéwas typed directly or pasted from another source — some sources yield a visually-identical but different Unicode sequence, e.g. a combining accent, which can behave differently than the precomposedéused in the existing tests)?That will help pin down whether this is a real regression in a specific version/input shape vs. an environment-specific character encoding issue.