[Bug] sideEffects does not work in turbopack
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 263
- Forks
- 50
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 16
Description
Version
1.0.0
Link to Minimal Reproduction
null
Steps to Reproduce
- create a nextjs app
- import VTable
- npm run dev (新版nextjs默认使用turbopack打包，旧版需要加--turbo参数)
Current Behavior
Expected Behavior
side effects can work when use turbopack
Environment
- OS:
- Browser:
- Framework:
Any additional comments?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with VRender 1.0.0 in a Next.js app, running npm run dev with Turbopack or --turbo on older Next.js versions. The issue names no source files or tests and provides no minimal reproduction, so first isolate how sideEffects behaves under Turbopack; done means side effects work as expected in that setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100