archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

README: fix "Routing with lazy component loading" blob (#915)

Browse source 
Looks like `<Link>` was replaced with `\n` on accident
This commit is contained in:
Stephen Mathieson 2017-01-28 16:59:29 -08:00 committed by Arunoda Susiripala
parent 0820204646
commit ac2a963c9c
1 changed files with 1 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -588,8 +588,7 @@ No in that it enforces a _structure_ so that we can do more advanced things like
- Automatic code splitting - Automatic code splitting
In addition, Next.js provides two built-in features that are critical for every single website: In addition, Next.js provides two built-in features that are critical for every single website:
- Routing with lazy component loading: ` - Routing with lazy component loading: `<Link>` (by importing `next/link`)
>` (by importing `next/link`)
- A way for components to alter `<head>`: `<Head>` (by importing `next/head`) - A way for components to alter `<head>`: `<Head>` (by importing `next/head`)
If you want to create re-usable React components that you can embed in your Next.js app or other React applications, using `create-react-app` is a great idea. You can later `import` it and keep your codebase clean! If you want to create re-usable React components that you can embed in your Next.js app or other React applications, using `create-react-app` is a great idea. You can later `import` it and keep your codebase clean!