swc-project / swc-project/swc-node
@swc-node/register@1.10.2 breaks for Yarn PnP
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 95
- Avg merge
- 14d 11h
- Merged PRs (30d)
- 1
Description
As mentioned here, the changes to use oxc-resolver breaks projects that rely on Yarn PnP. I suggest we provide some fallback TS resolution for Yarn PnP.
Contributor guide
No contributing guide indexed for this repository
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 with the changes that introduced oxc-resolver and the linked discussion in issue 804, then reproduce the failure in a Yarn PnP project. Done means @swc-node/register resolves TypeScript successfully for projects using Yarn PnP without regressing the existing resolver behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100