- 05 Feb, 2018 10 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Arunoda Susiripala authored
This reverts commit fa03f0b9.
-
Tim Neutkens authored
-
Tim Neutkens authored
* Add tests for universal webpack * Move tests to next-plugins * Remove obsolete files * Remove removed page * Remove tests * Rename test suite
-
Tim Neutkens authored
-
Tim Neutkens authored
* Add update notifier * Make update notifier work with custom server
-
Tomáš Witek authored
-
Tim Huff authored
Got this fix from issue #2302. Libraries like `font-awesome` are pretty common. Indicating how to get them to work should be indicated in the `README.md` (if not added to the example)
-
Arunoda Susiripala authored
-
- 04 Feb, 2018 5 commits
-
-
Henric Malmberg authored
* do not use window.history if inside iframe * Move security related test cases into a its own file. * Removes the unused renderScript function * Add a nerv example. (#3573) * Add a nerv example. * Fix for indentation/style * Fix for name * warn user about browser history if next.js used in iframe
-
M Pacer authored
* move imports into files using lettable operators, remove rxjs-library * refactor to be more in keeping with redux conventions from the single reducer.js, I split the functionality into actionTypes (actionTypes.js), actions (actions.js), and epics (epics.js). Most of the fetching should be done in an epic, but that requires introducing a new action and so was better in a separate commit. * switch to fetching on the front-end via an epic The fetching previously was triggered using an api call that had side effects, but was triggered from inside of an epic and was not an action. Now calls on the front-end all of the api calls are occuring via an action through fetchCharacterEpic. This does not remove the api.js file as I have not yet been able to get the epic to trigger correctly on the server-side, thus the api.fetchCharacter call is awaited in getInitialProps for initialising the state serverSide. * remove need for the serverSide api by directly handling the dispatch This still seems to be an incomplete solution to the problem as it circumvents the standard redux event flow on the serverside. However, it does obey the spirit of the redux event flow (as it passes an Observable of an action into the epic to then trigger other actions). Additionally, this removes the problem of code duplication. * update README.md and move lib/ to redux/ * Fix linting
-
Jon Espen Kvisler authored
* use getDataFromTree in browser * formatting * removed ssrMode argument, not needed
-
Arunoda Susiripala authored
* Add an example showing how to use polyfills. * Add some example polyfills. * Fix a typo.
-
Tim Neutkens authored
-
- 03 Feb, 2018 4 commits
-
-
John Polacek authored
-
Arunoda Susiripala authored
Also make sure to init assetPrefix in next/asset in the context of next-export.
-
Chris authored
* Add example on how to pass data through js api during SSR Requested in #1117 * Use content negotiation instead of a separate route * Codereview feedback * Move security related test cases into a its own file. * Removes the unused renderScript function * Add a nerv example. (#3573) * Add a nerv example. * Fix for indentation/style * Fix for name
-
John Polacek authored
-
- 02 Feb, 2018 5 commits
-
-
Tim Neutkens authored
-
Arunoda Susiripala authored
* Allow next/asset to work properly with dynamic assetPrefix Now we use webpack's publicPath via client side. * Add test cases for dynamic assetPrefix and next/asset.
-
Frank Dai authored
-
Shogun Sea authored
-
Arunoda Susiripala authored
* Introduce the setAssetPrefix API for dynamic assetPrefix. * Remove unwanted node_modules dir in a test dir. * Change test main description.
-
- 01 Feb, 2018 7 commits
-
-
Tim Neutkens authored
-
Arunoda Susiripala authored
* Use the latest path-to-regexp for path-match. * Fix the error route resolving. * Give proper credit to path-match * Remove an unwanted route. * Revert "Remove an unwanted route." This reverts commit 523c1687da8ddd499819e70df81567ec208e5998. * Add a comment why we need to keep _error.js route.
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Arunoda Susiripala authored
This is needed for multi-zones feature
-
- 31 Jan, 2018 9 commits
-
-
Luis Fernando Alvarez D authored
* next export will expand symlinks now * Make sure next export doesn't includes _document.js in windows * avoid a client side not found page when navigating to a custom route
-
Tim Neutkens authored
* Check if Component is defined * Add comment * Fix linting
-
Tim Neutkens authored
-
Luc authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Jerome Fitzgerald authored
* [fix] apollo-redux: Separate out entire example #3463 Apollo and Redux are completely separate ways of managing state. This example serves as a conduit if you were using Apollo 1.X with Redux, and are migrating to Apollo 2.x, however, you have chosen not to manage your entire application state within Apollo (`apollo-link-state`). There is no "withData" function that allows you to call either/or. You must call "withRedux" and/or "withApollo" on your Component. They can be combined in the example at `index.js` or remain separate as seen in `apollo.js` and `redux.js`. Going forward, this example may go the way of the dodo. * [chore] reformat code to match next syntax Localize prettier sometimes has a mind of its own.
😄 ️ * Fix linting -
Brice BERNARD authored
-
Stephen Mathieson authored
This patch adds an example of a Next.js app using analytics. A custom document injects the [Segment](https://segment.com) bootstrapping snippet into the `<head>`, allowing "page" and "track" calls to be made. An issue came up in CNA asking how we handle this in our apps (see https://github.com/segmentio/create-next-app/issues/24), so I figure an "official example" could help. NOTE: I am affiliated with Segment.
-