microsoft / microsoft/TypeScript

Fatal error during resolution through `RootLength`

Open
#63,834 1 comment 1 reaction 2 assignees View on GitHub

@DanielRosenwasser is already working on this.

Since Jun 8, 2026.

  • #4248 by @copilot-swe-agent — closed without merging
Crash
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

No repro, but error occurs at this line

panic(fmt.Sprintf("vfs: path %q is not absolute", p))

with this stack trace

internal/vfs/internal.RootLength()
	internal/vfs/internal/internal.go:23
internal/vfs/internal.SplitPath()
	internal/vfs/internal/internal.go:32
internal/vfs/internal.(*Common).RootAndPath()
	internal/vfs/internal/internal.go:39
internal/vfs/internal.(*Common).Stat()
	internal/vfs/internal/internal.go:47
internal/vfs/internal.(*Common).FileExists()
	internal/vfs/internal/internal.go:59
internal/vfs/osvfs.(*osFS).FileExists()
	internal/vfs/osvfs/os.go:104
internal/vfs/cachedvfs.(*FS).FileExists()
	internal/vfs/cachedvfs/cachedvfs.go:71
internal/project.(*snapshotFSBuilder).FileExists()
	internal/project/snapshotfs.go:311
internal/project.(*sourceFS).FileExists()
	internal/project/snapshotfs.go:715
internal/module.(*resolutionState).tryFileLookup()
	internal/module/resolver.go:1595
internal/module.(*resolutionState).tryFile()
	internal/module/resolver.go:1580
internal/module.(*resolutionState).tryExtension()
	internal/module/resolver.go:1568
internal/module.(*resolutionState).tryAddingExtensions()
	internal/module/resolver.go:1530
internal/module.(*resolutionState).loadModuleFromFile()
	internal/module/resolver.go:1425
internal/module.(*resolutionState).nodeLoadModuleByRelativeName()
	internal/module/resolver.go:1391
internal/module.(*resolutionState).resolveNodeLikeWorker()
	internal/module/resolver.go:575
internal/module.(*resolutionState).resolveNodeLike()

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.