1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Commit graph

7 commits

Author SHA1 Message Date
Sébastien Dubois a66ff658f4 Fix link (#789)
* Fix link

* Fix links
2017-01-16 18:23:24 -03:00
Dan Zajdband f6ece560e4 Add/data fetch example (#485)
* Added data fetch example

* Finished updating examples install instructions and added data-fetch example to main readme
2016-12-23 08:05:49 +09:00
nkzawa cae706d7b7 examples: use HTTPS URL 2016-12-22 18:14:12 +09:00
nkzawa aa630279e6 examples: simplify download instruction 2016-12-22 18:07:54 +09:00
Dan Zajdband c5d69f0585 Add/move examples (#470)
* Added redux and styled components (wip) examples.

* Updated examples readmes and package.json

* Fixed styled-components example
2016-12-21 21:10:54 -08:00
Guillermo Rauch 1af5bc98bb Update README.md 2016-12-20 12:45:27 -08:00
Arunoda Susiripala 36abdc77c5 Prefetch pages with Service Workers (#375)
* Register the service worker.

* Update prefetcher code to do prefetching.

* Implement the core prefetching API.
support "import <Link>, { prefetch } from 'next/prefetch'"

* Implement a better communication system with the service worker.

* Add a separate example for prefetching

* Fix some typos.

* Initiate service worker support even prefetching is not used.
This is pretty important since initiating will reset the cache.
If we don't do this, it's possible to have old cached resources
after the user decided to remove all of the prefetching logic.
In this case, even the page didn't prefetch it'll use the
previously cached pages. That because of there might be a already running
service worker.

* Use url module to get pathname.

* Move prefetcher code to the client from pages
Now we also do a webpack build for the prefetcher code.

* Add prefetching docs to the README.md

* Fix some typo.

* Register service worker only if asked to prefetch
We also clean the cache always, even we initialize
the service worker or not.
2016-12-15 11:13:40 -08:00