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

8 commits

Author SHA1 Message Date
Dan Zajdband bacb42ead4 Updated README with new features and code fixes (#444)
* Updated README with new features and code fixes

* Removed staticMarkup option from docs.

* Fixed quiet parameter info.
2016-12-20 14:57:11 -08:00
Guillermo Rauch 1af5bc98bb Update README.md 2016-12-20 12:45:27 -08:00
Guillermo Rauch 9056116c5b Update Header.js 2016-12-20 12:44:23 -08:00
Guillermo Rauch 376661254d Update index.js 2016-12-20 12:41:40 -08:00
Guillermo Rauch a27f6b0af6 Update features.js 2016-12-20 12:41:26 -08:00
Guillermo Rauch 8129eea237 Update contact.js 2016-12-20 12:41:15 -08:00
Guillermo Rauch 36255e5c5d Update about.js 2016-12-20 12:41:01 -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