swc-project/swc

Alternative package manager support for the module resolution

Open

#3,247 opened on Jan 13, 2022

View on GitHub
 (20 comments) (24 reactions) (0 assignees)Rust (33,411 stars) (1,389 forks)batch import
enhancementhelp wanted

Description

Describe the feature

Since the currently implemented plugin resolve algorithm relies on the node_modules structure, it doesn't work with alternative module linking approaches like ones from pnpm and Yarn Berry. While directly pointing at the WASM binary is implemented as a temporary workaround, this should be covered with a more elegant and user-friendly approach.

Initially discussed in the Discord channel

Babel plugin or link to the feature description

No response

Additional context

No response

Contributor guide

Tech stack
rustnodejs
Domain
toolingbuild system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Rust programming knowledgeNode.js module resolutionpnpm and Yarn Berry concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the current plugin resolution algorithm in the swc codebase, likely in the plugin system source under crates/. Understand how it relies on node modules. Explore how pnpm's hoisting and Yarn Berry's PnP mode differ. Look at existing plugins and the temporary workaround of pointing to WASM binary. Refer to the Discord discussion linked for additional context. Identify the key changes needed to support alternative package manager structures.