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

Bug: `FileTreePreparedInput` contains a `Symbol` key and is not serializable

Open
  • Is something wrong?
#1,109 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@michaltarasiuk is already working on this.

Since Aug 31, 2026.

  • #1110 by @michaltarasiuk — 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
next.js, react, typescript
Domain
frontend

Research direction

Start by reading the definitions of FileTreePreparedInput and prepareFileTreeInput, then trace how the prepared input is passed across the React Server Component boundary. Reproduce the reported serialization error with the Server Component and Client Component examples in the issue. Done means the prepared input can cross that boundary without the Symbol-property error; an open linked pull request indicates work is already underway.

Written by the indexing model from the issue text.

Description

bug
Prerequisites
Describe the issue

FileTreePreparedInput includes a Symbol-keyed property (pathStorePreparedInputKind), making it non-serializable.

Passing this object from a Next.js Server Component to a Client Component triggers a serialization error, as Symbol values cannot cross the React Server Component (RSC) boundary.

Reproduction

page.tsx (Server Component):

export default async function Page({ params }: { params: Promise<{ projectId: string }> }) {
  const { projectId } = await params;
  const paths = await fetchProjectPaths(projectId);
  const preparedInput = prepareFileTreeInput(paths);

  return <FileTreeClient preparedInput={preparedInput} />;
}

file-tree.tsx (Client Component):

'use client';

export function FileTreeClient({ preparedInput }: { preparedInput: FileTreePreparedInput }) {
  const { model } = useFileTree({ preparedInput });

  return <FileTree model={model} />;
}

Error output:

Error: Only plain objects can be passed to Client Components from Server Components. Objects with symbol properties like pathStorePreparedInputKind are not supported.
  {preparedInput: {paths: ..., preparedPaths: ...}}
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What browser(s) are you seeing the problem on?

No response

What version of @pierre/diffs are you using?

1.0.0-beta.6

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

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.