Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug(trees): deeply nested single folder paths don't render nicely

Open
#941 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@pablofdezr is already working on this.

Since Jul 15, 2026.

  • #997 by @pablofdezr — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start by locating the tree rendering code and reproduce the issue with a deeply nested path containing only one directory at each level. Check how the path is truncated in Chrome, especially whether any path characters remain visible. Done means the rendered tree shows part of the path rather than only an ellipsis; an open pull request is already linked to this issue.

Written by the indexing model from the issue text.

Description

bug trees
Prerequisites
Describe the issue

Using flattenEmptyDirectories is a workaround but not a very user friendly one either IMO. vscode concatenates everythig and cuts it at the end. That way you see the beginning of the path. The extreme form of the current implementation is to only see the ellipsis and not a single character of the actual path

Image
Reproduction

use tree with deeply nested path only containing a single directory (java hierarchy for instance)

What browser(s) are you seeing the problem on?

Chrome

What version of @pierre/diffs are you using?

1.0.0-beta.5

Dominant language
TypeScript
Stars
6.2k
Forks
226
Avg merge
1d 12h
Merged PRs (30d)
34

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from pierrecomputer/pierre

All issues in pierrecomputer/pierre

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.