* Allow etags to be disabled with config option
- CR Change: Rename option to generateEtags
- CR Change: Add tests for etag generation
- CR Change: Refactor to use next.config.js
- Update documentation
* Use renderOpts instead of passing nextConfig
* Removed combine-assets-plugin, since its very broken
* Bundle everything into app.js on production build
* Clean up
* Removed app.js from server routes
* Renamed app.js -> main.js and removed commons from loading
* Remove commons and react CommonChunks
* Removed the commons route
* Killing the entire build-stats hack for app.js
* Removed unused md5-file package
* Add next/config
* Set config on server start / client render
* Add documentation for next/config
* Add next/config support for next export
* Fix test
* Use the correct name
* Set default to empty object on the client side
* Add config tests
* Rename config to runtimeConfig
* Fix SSR error handling.
* Remove unwanted console.logs
* Fix a typo.
* Fix current tests.
* Add a new test case for this case.
* Error should only be logged if it is not a 404
* Allow next.config.js to export a function
* Expose phases to the configuration function
* Use same value as variable name
* Add next/constants
* Add documentation for config function / phases
* Add constants.js to npm bundle
* Remove special error script handling.
As a result of that, we can't detect 500 errors and buildIdMismatch via client side.
* Fix failing test cases.
* Refactor the code base.
* Remove Router.onAppUpdated
* [SSR] Use relative paths in dynamic import output code
Now we use relative paths in the output code of dynamic import
in the server side.
* Remove unwanted constructor.
This reverts `fb7c862` per @timneutkens
- Removes the errors/*.md associated
- Puts back `poweredByHeader` for `next.config.js`
- Reincorporates test:
X-Powered-By header
✓ should set it by default (3ms)
✓ should not set it when poweredByHeader==false (5ms)
Also tested with `yarn link` and verified.
* Make page require faster
* Add windows search/replace
* Use normalize instead of resolve
* Add remaining tests
* Use sep instead of /
* Add test files
* Make component require faster
* Add console.error
* Make pageExtensions configurable
* Remove resolve.js
* Add test for `.jsx`
* Also resolve `/nav/index` and the likes
* Normalize page paths
* Use config passed off by webpack
* Render error on the client without fetching additional scripts.
* Fix test cases.
* Remove unused '_document' page in ensurePage logic
* Remove console.error when page is not found
* Make page require faster
* Add windows search/replace
* Use normalize instead of resolve
* Add remaining tests
* Use sep instead of /
* Add test files
* Make component require faster
* Add console.error
* Remove aliasing of react and react-dom
We need that functionality, but React does it automatically.
So, we don't need to do that.
This also fixes#3711 otherwise we need to add a few more aliases.
* Revert "Remove aliasing of react and react-dom"
This reverts commit 929d9567bbdc3f369f13888e846e848a25c9c261.
* Allow to import modules like 'react-dom/server'.
We do this by doing an extact match for 'react' and 'react-dom'
* 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
* Release 5.0.0
* Add multi-zones docs. (#3688)
* Include next/dist/pages
* Fix linting
* 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.
* 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.
