vercel / vercel/next.js

[turbopack] super class not able to set properties on derived class

Open
#80,708 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Turbopack
Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

Link to the code that reproduces this issue

https://github.com/johansunden/my-app

To Reproduce

I am re-opening https://github.com/vercel/next.js/issues/77467

I am also encountering this issue and the original issue was closed without resolution.

The bottom line is, dev and dev --turbo behave differently and that shouldn't be the case.

The usage of "useDefineForClassFields": false does not resolve this issue either.

Current vs. Expected behavior

Derived classes should have defined properties when defined in the super class constructor.

Provide environment information
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:52:00 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6031
  Available memory (MB): 36864
  Available CPU cores: 14
Binaries:
  Node: 22.16.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.3.3 // There is a newer version (15.3.4) available, upgrade recommended! 
  eslint-config-next: 15.2.3
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A
 ⚠ There is a newer version (15.3.4) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

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.

Research direction

Start with the linked reproduction at github.com/johansunden/my-app and compare dev with dev --turbo using the reported class inheritance case. Confirm whether the superclass constructor's properties are missing from the derived class, then trace the relevant Turbopack path; done means both modes define those properties consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nextjs, typescript
Domain
build-system, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.