Allow mocking and aliasing externals
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
When bundling and inlining dependencies, we have a chance to use rollup configuration to mock some unwanted external dependencies using unenv (nuxt uses this for example for vue deps).
This is not possible when externalizing those dependencies and using nitro externals + nft to track them.
With a new option like externals.alias, we can instruct nft to use a mocked and auto-generated package instead. Previously it wasn't possible but with new implementation of externals plugin with full-control over dep graph, we can do this.
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 reading the externalization implementation and the new externals plugin mentioned in the issue, then compare it with the linked Nuxt example in packages/nuxt/src/core/nitro.ts. Trace how nft receives the dependency graph and define what externals.alias should generate and how a mocked external should be selected. Done means the option supports aliasing an external dependency and is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rollup, typescript
- Domain
- backend, build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100