agentleFS
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/ts1261-filename-casing/SKILL.md

ts1261-filename-casing

Skill1k starsChanged 28 days agoBSD-3-ClauseView on GitHub

Fix TS1261 when TypeScript reports two paths that differ only in casing (import vs include vs git index). Use when compile shows error 1261 or "Already included file name ... differs from file name ... only in casing".

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

Files
SKILL.md

TS1261 (filename casing)

Problem

Diagnostic 1261 in typescript (Already_included_file_name_0_differs_from_file_name_1_only_in_casing): one path comes from an import, another from include / program — same file on a case-insensitive disk, different casing in the string.

Typical cause: git tracks fooBar.ts but imports ./FooBar; or a case-only rename left the index with old casing.

Fix

Canonical name = what imports use (and consistent Pascal/camel across repo).

Case-insensitive FS (macOS default, Windows): case-only renames need a temporary middle name so git and the filesystem both update.

cd path/to/dir
git mv WrongCaseName.ts _tmp_rename.ts
git mv _tmp_rename.ts RightCaseName.ts

Then npm run compile.

Why not a single git mv?

git mv a.ts A.ts often no-ops or fails when a and A resolve to the same path — the two-step move is the reliable fix.

git rm / index

Goal is an index entry whose path string matches imports. git rm --cached <wrong-cased-path> removes that index entry; you still must put content on disk under the right cased name (again: use intermediate mv on case-insensitive FS). Two-step git mv updates index + working tree in one workflow without a detached delete step.

Verify

  • npm run compile
  • git ls-files path/to/dir | grep -i <basename> shows one line, casing matches imports

Checklist

  • Read TS1261 lines: identify both casing spellings
  • Choose spelling that matches existing imports
  • Two-step git mv if case-only change on case-insensitive FS
  • Re-run compile

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.