Skip to content

React.lazy() #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gaearon merged 3 commits into from
Oct 23, 2018
Merged

React.lazy() #64

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7c2b878
React.lazy()
gaearon Oct 19, 2018
cf3da2d
Mention future named export support proposal
gaearon Oct 19, 2018
bb55746
Clarify and fix typo
gaearon Oct 19, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Clarify and fix typo
  • Loading branch information
@gaearon
gaearon authored Oct 19, 2018
commit bb5574633bd3ad412d1c76ec08691553d55bb203
6 changes: 5 additions & 1 deletion text/0000-lazy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ Start Date: 2018-10-19

`React.lazy` adds first-class support for code splitting components to React. It takes a module object and returns a special component type.

>Note
>
>This RFC is intentionally scoped to supporting default imports. We may in the future submit another RFC concerning named imports. In the meantime you can also implement support for named imports in userland with a lower-level Suspense API (to be discussed in another RFC).

# Basic example

```js
Expand Down Expand Up @@ -68,7 +72,7 @@ The second part of the question is why don't we still _allow_ passing something
const Button = lazy(async () => {
const Components = await import('./components');
// Resolve to named export:
return components.Button;
return Components.Button;
});
```

Expand Down