Enhance default export handling to return .default by default for main APIs #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Addresses GitHub issue #15: "It may be a good idea to return
.defaultby default"This enhancement improves the user experience by automatically returning the default export for packages where it's the primary API (like axios), while preserving backwards compatibility and existing behavior for packages that users commonly destructure from.
Changes
baseUsefunction in all three variants (use.js, use.mjs, use.cjs)Behavior
Before this change:
After this change:
Heuristic Logic
The enhancement uses a smart heuristic that returns the default export when:
defaultexport that is a function$,sh,cli,cmd,exec,run,create,make,build,test)This ensures:
{ $ }destructuringTest Results
const axios = await use('axios')const { $ } = await use('command-stream')const _ = await use('lodash')Test Plan
Comprehensive testing included:
🤖 Generated with Claude Code
Resolves #15