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

Feature: support custom folder icons in file-tree

Open
#1,069 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
47/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start by locating the file-tree implementation and reading how custom file icons are currently supported. Then trace how folder names and open/closed state are represented in the tree. Done means users can provide custom folder icons, including name-specific and open/closed variants.

Written by the indexing model from the issue text.

Description

enhancement
Prerequisites
Proposal

The ability to have custom folder icons the same way we can modify file icons in the file-tree. Including the ability to have custom folder icons based on folder names, as well as state between "open" and "closed" folders since some icon packs support different designs based on such.

Motivation and context

Many projects of mine which have used the file tree have custom file icons, and I've found that the default chevron style folder/directory doesn't match the style and design of the file tree very well at all.

To provide an example:

Image

I'm using material icons here, and it would look great if the chevrons were indevidual folder icons instead.

Here's an example if it did: (from better-hub.com)

Image
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.