- 02 2月, 2018 3 次提交
-
-
由 Tim Neutkens 提交于
-
由 Arunoda Susiripala 提交于
* 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 提交于
-
- 01 2月, 2018 6 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Arunoda Susiripala 提交于
This is needed for multi-zones feature
-
由 Luis Fernando Alvarez D 提交于
* 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 提交于
* Check if Component is defined * Add comment * Fix linting
-
- 31 1月, 2018 16 次提交
-
-
由 Tim Neutkens 提交于
-
由 Luc 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Jerome Fitzgerald 提交于
* [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 提交于
-
由 Stephen Mathieson 提交于
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.
-
由 Logan McAnsh 提交于
* add Polka server example * Update package.json * Fix linting
-
由 Sergio Xalambrí 提交于
-
由 Tim Neutkens 提交于
-
由 Luis Fernando Alvarez D 提交于
* next export will expand symlinks now * Make sure next export doesn't includes _document.js in windows
-
由 Alex Indigo 提交于
* Added `with-ioc` example * pre-compile deps until we get nextjs magic working
-
由 Arunoda Susiripala 提交于
* Make sure dynamic imports works on Windows * Fix an issue with the load test firmware. * Fix symlink creation on Unix
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
-
- 30 1月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
* Speed up next build * Document webpack config * Speed up next build * Remove comment * Add comment * Clean up rules * Add comments * Run in parallel * Push plugins seperately * Create a new chunk for react * Don’t uglify react since it’s already uglified. Move react to commons in development * Use the minified version directly * Re-add globpattern * Move loaders into a separate variable * Add comment linking to Dan’s explanation * Remove dot * Add universal webpack * Initial dev support * Fix linting * Add changes from Arunoda's work * Made next dev works. But super slow and no HMR support. * Fix client side hot reload * Server side hmr * Only in dev * Add on-demand-entries client + hot-middleware * Add .babelrc support * Speed up on demand entries by running in parallel * Serve static generated files * Add missing config in dev * Add sass support * Add support for .map * Add cssloader config and fix .jsx support * Rename * use same defaults as css-loader. Fix linting * Add NoEmitErrorsPlugin * Add clientBootstrap * Use webpackhotmiddleware on the multi compiler * alpha.3 * Use babel 16.2.x * Fix reloading after error * Remove comment * Release 5.0.0-univeral-alpha.1 * Remove check for React 16 * Release 5.0.0-universal-alpha.2 * React hot loader v4 * Use our static file rendering machanism to serve pages. This should work well since the file path for a page is predictable. * Release 5.0.0-universal-alpha.3 * Remove optional loaders * Release 5.0.0-universal-alpha.4 * Remove clientBootstrap * Remove renderScript * Make sure pages bundles are served correctly * Remove unused import * Revert to using the same code as canary * Fix hot loader * Release 5.0.0-universal-alpha.5 * Check if externals dir exist before applying config * Add typescript support * Add support for transpiling certain packages in node_modules Thanks to @giuseppeg’s work in https://github.com/zeit/next.js/pull/3319 * Add BABEL_DISABLE_CACHE support * Make sourcemaps in production opt-in * Revert "Add support for transpiling certain packages in node_modules" This reverts commit d4b1d9babfb4b9ed4f4b12d56d52dee233e862da. In favor of a better api around this. * Support typescript through next.config.js * Remove comments * Bring back commons.js calculation * Remove unused dependencies * Move base.config.js to webpack.js * Make sure to only invalidate webpackDevMiddleware one after other. * Allow babel-loder caching by default. * Add comment about preact support * Bring back buildir replace * Remove obsolete plugin * Remove build replace, speed up build * Resolve page entries like pages/day/index.js to pages/day.js * Add componentDidCatch back * Compile to bundles * Use config.distDir everywhere * Make sure the file is an array * Remove console.log * Apply optimization to uglifyjs * Add comment pointing to source * Create entries the same way in dev and production * Remove unused and broken pagesGlobPattern * day/index.js is automatically turned into day.js at build time * Remove poweredByHeader option * Load pages with the correct path. * Release 5.0.0-universal-alpha.6 * Make sure react-dom/server can be overwritten by module-alias * Only add react-hot-loader babel plugin in dev * Release 5.0.0-universal-alpha.7 * Revert tests * Release 5.0.0-universal-alpha.10 * Make sure next/head is working properly. * Add wepack alias for 'next' back. * Make sure overriding className in next/head works * Alias react too * Add missing r * Fragment fallback has to wrap the children * Use min.js * Remove css.js * Remove wallaby.js * Release 5.0.0-universal-alpha.11 * Resolve relative to workdir instead of next * Make sure we touch the right file * Resolve next modules * Remove dotjsx removal plugins since we use webpack on the server * Revert "Resolve relative to workdir instead of next" This reverts commit a13f3e4ab565df9e2c9a3dfc8eb4009c0c2e02ed. * Externalize any locally loaded module lives outside of app dir. * Remove server aliases * Check node_modules reliably * Add symlink to next for tests * Make sure dynamic imports work locally. This is why we need it: https://github.com/webpack/webpack/blob/b545b519b2024e3f8be3041385bd326bf5d24449/lib/MainTemplate.js#L68 We need to have the finally clause in the above in __webpack_require__. webpack output option strictModuleExceptionHandling does that. * dynmaic -> dynamic * Remove webpack-node-externals * Make sure dynamic imports support SSR. * Remove css support in favor of next-css * Make sure we load path from `/` since it’s included in the path matching * Catch when ensurepage couldn’t be fulfilled for `.js.map` * Register require cache flusher for both client and server * Add comment explaining this is to facilitate hot reloading * Only load module when needed * Remove unused modules * Release 5.0.0-universal-alpha.12 * Only log the `found babel` message once * Make sure ondemand entries working correctly. Now we are just using a single instance of OnDemandEntryHandler. * Better sourcemaps * Release 5.0.0-universal-alpha.13 * Lock uglify version to 1.1.6 * Release 5.0.0-universal-alpha.14 * Fix a typo. * Introduce multi-zones support for mircofrontends * Add section on css
-
- 27 1月, 2018 3 次提交
-
-
由 Saro Vindigni 提交于
-
由 Gavin 提交于
Problem description: - Cannot find module 'redux-devtools-extension'
-
由 Shaleen Jain 提交于
-
- 25 1月, 2018 1 次提交
-
-
由 Connor Bär 提交于
-
- 13 1月, 2018 9 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Arunoda Susiripala 提交于
-
由 Arunoda Susiripala 提交于
-
由 Arunoda Susiripala 提交于
This should work well since the file path for a page is predictable.
-
- 12 1月, 2018 1 次提交
-
-
由 Leo Lamprecht 提交于
-