next.js
fix: mixing namespace import and named import client components
#64809

Merged

fix: mixing namespace import and named import client components #64809

huozhi merged 8 commits into canary from fix/tree-shaking-import-wildcard

repro

e6f6373f

fix: mixing wildcard import and named import client components

abf2bdc6

ijjk added created-by: Next.js team

ijjk added tests

ijjk added type: next

merge namespace and named imports into *

2e67d24b

refactor

a36b73bc

huozhi marked this pull request as ready for review 2 years ago

huozhi requested a review from

timneutkens 2 years ago

huozhi requested a review from

ijjk 2 years ago

huozhi requested a review from

shuding 2 years ago

huozhi requested a review from

ztanner 2 years ago

huozhi requested a review from

feedthejim 2 years ago

huozhi requested a review 2 years ago

huozhi requested a review from

wyattjoh 2 years ago

rename

b965f854

huozhi changed the title ~~fix: mixing wildcard import and named import client components~~ fix: mixing namespace import and named import client components 2 years ago

shuding commented on 2024-04-21

add more test

a56105d7

explain

5fdcc141

huozhi requested a review from

shuding 2 years ago

Merge branch 'canary' into fix/tree-shaking-import-wildcard

6bc015b8

shuding approved these changes on 2024-04-22

huozhi merged 7404ea4c into canary 2 years ago

huozhi deleted the fix/tree-shaking-import-wildcard branch 2 years ago

github-actions added locked

github-actions locked as resolved and limited conversation to collaborators 2 years ago

Reviewers

shuding

timneutkens

ijjk

ztanner

feedthejim

wyattjoh

Assignees

No one assigned

Labels

type: next created-by: Next.js team locked tests

Milestone

No milestone

next.js fix: mixing namespace import and named import client components #64809 Merged

fix: mixing namespace import and named import client components #64809

next.js
fix: mixing namespace import and named import client components
#64809

Merged