software-mansion / software-mansion/TypeGPU
chore: Check why named import `tgpu` is better treeshakable
Open
Nobody has claimed this yet.
exploration
good first issue
- Dominant language
- TypeScript
- Stars
- 3.2k
- Forks
- 122
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 34
Description
This is better treeshakable:
import { tgpu } from 'typegpu/$built$';
console.log(tgpu.lazy);
Than this:
import tgpu from 'typegpu/$built$';
console.log(tgpu.lazy);
We should investigate why. This makes a tree-shake table appear in each PR.
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 from the typegpu/$built$ entry point and compare the named and default import forms shown in the issue. Reproduce their tree-shaking behavior in the project’s existing build output, then identify and document why the named import produces a tree-shake table and what change, if any, is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100