- 23 4月, 2019 3 次提交
-
-
由 Pierre de la Martinière 提交于
* Add --no-subfolders argument to next export * Use experimental.exportTrailingSlash instead of a cli flag * Add experimental.exportTrailingSlash documentation * Add tests for export with experimental.exportTrailingSlash * Remove docs * Remove comment
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
* Cache Babel and AutoDll plugin in `dirDir/cache` * Extract code
-
- 22 4月, 2019 8 次提交
-
-
由 JJ Kasper 提交于
* Make styles compatible in AMP mode * bump * Update to parse styles from fragment for backwards compat in AMP mode * Add test for AMP styles fragment support
-
由 JJ Kasper 提交于
* Update to use babel plugin with webpack plugin to remove AMP client bundles since they are not used * Remove acorn dependency since it isn't used
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
The new version of Terser seems to be significantly slower than the previous. I wanted to see what our stats PR says.
-
由 JJ Kasper 提交于
We also close the connection when the window is in the background and re-connect when it is brought to the foreground. This prevents us from using up too many connections.
-
由 Luis Fernando Alvarez D 提交于
Related to [this spectrum post](https://spectrum.chat/next-js/general/next-8-minor-update-breaks-dynamic-import-in-jest-tests~1e7b58e7-e301-4ef9-9de4-eef6ed3639d4). I'm not removing the `babel-plugin-dynamic-import-node` package as it's going to be used by #7016
-
由 Fredrik Höglund 提交于
This PR adds the `_error`-page as an `404.html`-export, even when it is not explicitly defined in a custom `exportPathMap`. It also fixes two false negative tests related to this. Previously the tests were matching the fallback 404-page from the test-server, rather than the `404.html`-page from next, which was actually not being generated. The test server is also not set up to serve `/404.html` as `/404` which the tests now reflect. **Caveat** In its current state, this PR removes `/404.html` from the `defaultPathMap` passed to the custom `exportPathMap`-functions, since it instead adds it after that function is run. While it is possible that someone is relying on this to exist, it is to my knowledge undocumented and also unlikely to be used for anything but merging it into the custom pathMap. Since this would now merge `undefined` which would result in it being added later on anyway, I deemed it safe, but would be happy to undo that part of the PR if necessary as it was only cleanup. **Examples** As a way to demonstrate what this PR does, this is how examples changed: * `basic-export` - Behaviour is unchanged, still has a `404.html` * `with-static-export` - Now has a `404.html`
-
由 JJ Kasper 提交于
ampBindInitData check
-
- 20 4月, 2019 5 次提交
-
-
由 Connor Davis 提交于
-
由 JJ Kasper 提交于
-
由 Nathan Sculli 提交于
-
由 Nathan Sculli 提交于
- Use the new [@react.component] decorator for all of the react components and bindings. - Use the new react hook integrations for the counter component. - Add a `npm run dev:reason` and `npm run dev:next` commands to make running the build processes in separate terminals easier. I didn't update the README because I'm unsure if this is something that would be desired. - upgrade to reason react 0.7.0 - upgrade to react and react-dom 16.8.6 - upgrade to bs-platform 5.0.3 - upgrade to @babel/core 7.4.3
-
由 Yuki Takemoto 提交于
-
- 19 4月, 2019 1 次提交
-
-
由 Joe Haddad 提交于
-
- 18 4月, 2019 4 次提交
-
-
由 Jonathan Pollak 提交于
* feat(fela-example): replace old API with new ones
-
由 Koen Punt 提交于
instead of letter apollo rely on a global variable, we pass it explicitly to the HttpLink constructor.
-
由 JJ Kasper 提交于
This adds a test to the custom-server suite to make sure we don't regress on this
-
由 Andy O'Brien 提交于
-
- 17 4月, 2019 7 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
-
由 Joe Haddad 提交于
-
由 Connor Davis 提交于
-
由 JJ Kasper 提交于
-
由 Lucas Machado 提交于
-
- 16 4月, 2019 5 次提交
-
-
由 JJ Kasper 提交于
if `&=1` is used to point to the `amphtml` version of a page it get's escaped causing it to become `&amp=1` this fixes it to stay as `&=1` Closes: #7038
-
由 JJ Kasper 提交于
* Remove client bundles for AMP pages after build since they are not used * Remove trailing white space * Use async-sema to limit removing AMP client bundles * Bring AMP client bundle removing semaphore concurrency down to 20 * Don't check blocked pages when deleting AMP client bundles * Update client bundle removing for AMP pages * Add error handling for removing client AMP pages * rethrow error unless ENOENT during deleting AMP client pages * Handle error during removing AMP client pages the same during dev * Fix throwing instead of rejecting * Make sure next/config is set before requiring page * Update error check * return on reject * Fix next/config
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
This just removes the need for setting the experimental amp option
-
由 Luis Fernando Alvarez D 提交于
Added types to next/router
-
- 15 4月, 2019 7 次提交
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
* Update amphtml and canonical rels, put amp behind experimental flag again, and update checking for amp query * Fix typescript error * Re-add flag to next.config.js
-
由 JJ Kasper 提交于
* Add AMP docs to README * Update wording Co-Authored-By: Nijjk <jj@jjsweb.site> * remove extra space Co-Authored-By: Nijjk <jj@jjsweb.site> * Apply suggestions from code review Co-Authored-By: Nijjk <jj@jjsweb.site> * Apply suggestions from code review Co-Authored-By: Nijjk <jj@jjsweb.site>
-
由 Tim Neutkens 提交于
* Add x-powered-by * Remove ampEnabled type
-
由 Connor Davis 提交于
-