- 18 12月, 2018 2 次提交
-
-
由 Erik Nguyen 提交于
-
由 Tim Neutkens 提交于
-
- 16 12月, 2018 1 次提交
-
-
由 DevSide 提交于
This message is from @timneutkens after making changes: - Convert executables to Typescript - Remove `minimist` in favor of `arg` - Implement `--node-args` usage: `--node-args="--throw-deprecation"` - Adds tests for usage of the `next` cli
-
- 13 12月, 2018 1 次提交
-
-
由 Connor Davis 提交于
# Fixes https://github.com/zeit/next.js/issues/5674 This adds config option ```js // next.config.js module.exports = { crossOrigin: 'anonymous' } ``` This config option is defined in the webpack Define Plugin at build. `Head` and `NextScript` now use the config option, if it's not explicitly set on the element. This value is now passed to Webpack so it can add it to scripts that it loads. The value is now used in `PageLoader` (on the client) so it can add it to the scripts and links that it loads. Using `<Head crossOrigin>` or `<NextScript crossOrigin>` is now deprecated.
-
- 11 12月, 2018 1 次提交
-
-
由 Kenneth Luján Rosas 提交于
Per @timneutkens suggestion [here](https://github.com/zeit/next.js/pull/5631#issuecomment-440588455) I went ahead and gave a shot at trying to document `renderPage` usage. This PR: - Documents `renderPage` legacy and current usage.
-
- 04 12月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
* Add docs for returning `null` from generateBuildId * Add test for setting custom buildid * Fix linting
-
- 02 12月, 2018 1 次提交
-
-
由 Luc 提交于
-
- 28 11月, 2018 1 次提交
-
-
由 Ståle Pettersen 提交于
-
- 24 11月, 2018 1 次提交
-
-
由 Hozefa 提交于
Since glamorous is [no longer maintained](https://github.com/paypal/glamorous#status-unmaintained) removing it from readme.
-
- 21 11月, 2018 1 次提交
-
-
由 Curran Kelleher 提交于
I came across **Possible spelling mistakes** #5496 and noticed that the current wording could be improved both in terms of accuracy and succinctness.
-
- 19 11月, 2018 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 Sean Connolly 提交于
-
- 14 11月, 2018 1 次提交
-
-
由 Adam Lane 提交于
This alternative implementation of https://github.com/zeit/next.js/pull/5150 follows @timneutkens suggestion of using props. Fixes #5150 Fixes #3630
-
- 09 11月, 2018 1 次提交
-
-
由 Callum Locke 提交于
-
- 06 11月, 2018 1 次提交
-
-
由 Pieter De Decker 提交于
-
- 03 11月, 2018 1 次提交
-
-
由 Henrik Wenz 提交于
-
- 02 11月, 2018 1 次提交
-
-
由 Homer Chen 提交于
Hi Just add a space on README. That line should be same as [here](https://github.com/zeit/next.js/blob/canary/examples/using-with-router/components/ActiveLink.js#L10)
-
- 01 11月, 2018 1 次提交
-
-
由 Kosuke Yoshimura 提交于
* add description of importing _error.js * fix description of importing _error.js * delete .idea folder
-
- 27 10月, 2018 1 次提交
-
-
由 Dmitriy 提交于
* Fix readme * Fix spelling mistake Co-Authored-By: Ndipiash <dmitriytemn@gmail.com>
-
- 20 10月, 2018 1 次提交
-
-
由 Alexandre Cisneiros 提交于
Just a quick typo fix on Multi Zones documentation :)
-
- 10 10月, 2018 1 次提交
-
-
由 Adam Stankiewicz 提交于
* Show that <Head /> is needed for custom document * Add comment explaining required Document fields * Update README.md
-
- 08 10月, 2018 1 次提交
-
-
由 Henrik Wenz 提交于
-
- 06 10月, 2018 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
- 02 10月, 2018 1 次提交
-
-
由 Martin Beierling-Mutz 提交于
fixes #5355
-
- 01 10月, 2018 2 次提交
-
-
由 Evil Rabbit 提交于
-
由 Tim Neutkens 提交于
- Implements Lerna - Moves all source code into `packages/next` - Keeps integration tests in the root directory
-
- 29 9月, 2018 2 次提交
-
-
由 Shu Ding 提交于
- `<details>` and `<ul>` cannot be inside `<p>` and it will not be parsed correctly by the MDX tokenizer. - `sh` is not a valid language name for syntax highlighting libs (e.g. [highlight.js](https://github.com/highlightjs/highlight.js/tree/master/src/languages)).
-
由 Tim Neutkens 提交于
-
- 22 9月, 2018 1 次提交
-
-
由 Iago Bruno 提交于
I think it looks better for new people in JavaScript/React (and for my perfectionism
😄 ).
-
- 04 9月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
Related #4659 Adds the possibility for users to copy files inside of `exportPathMap`. This allows for adding `robots.txt` `sitemap.xml` etc. another use case is for https://github.com/hanford/next-offline, currently it's manually reading the buildId in `exportPathMap`. To allow users to do this we'll introduce a new parameter holding an object with the following keys: - `dev` - `true` when `exportPathMap` is being called in development. `false` when running `next export`. In development `exportPathMap` is used to define routes and behavior like copying files is not required. - `dir` - Absolute path to the project directory - `outDir` - Absolute path to the `out` directory (configurable with `-o` or `--outdir`). When `dev` is `true` the value of `outDir` will be `null`. - `distDir` - Absolute path to the `.next` directory (configurable using the `distDir` config key) - `buildId` - The buildId the export is running for Example usage: ```js // next.config.js const fs = require('fs') const {join} = require('path') const {promisify} = require('util') const copyFile = promisify(fs.copyFile) module.exports = { exportPathMap: async function (defaultPathMap, {dev, dir, outDir, distDir, buildId}) { if(dev) { return defaultPathMap } // This will copy robots.txt from your project root into the out directory await copyFile(join(dir, 'robots.txt'), join(outDir, 'robots.txt')) return defaultPathMap } } ```
-
- 03 9月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 22 8月, 2018 1 次提交
-
-
由 HaNdTriX 提交于
Depends on: https://github.com/zeit/next.js/pull/4988
-
- 20 8月, 2018 1 次提交
-
-
由 Leo Lamprecht 提交于
Previously, it was mistakenly located under @arunoda's personal account.
-
- 18 8月, 2018 1 次提交
-
-
由 HaNdTriX 提交于
As reported by @ranyitz the links in the documentation about ['What syntactic features are transpiled? How do I change them?'](https://github.com/zeit/next.js#faq) are broken. I updated the links and the text to reflect the latest changes. Closes #4974 Related https://github.com/zeit/next.js/commit/eb74ff4bf9e3b83edee346fc0dfa99e7e7cc086c
-
- 14 8月, 2018 2 次提交
-
-
由 Luc 提交于
Following https://github.com/zeit/next.js/pull/4950 Fix https://github.com/zeit/next.js/issues/4716 I'm not sure to understand this part, though : > Note: in order to programmatically change the route without triggering navigation and component-fetching, use `props.url.push` and `props.url.replace` within a component Is there a difference between : ```jsx export default () => <a onClick={() => Router.push('/about')}>About</a> ``` and ```jsx export default withRouter( () => <a onClick={() => props.router.push('/about')}>About</a> ) ``` ?
-
由 Luc 提交于
* replace componentWillReceiveProps by componentDidUpdate * replace props.url by withRouter HOC * fix deprecated `props.url` in with-shallow-routing example
-
- 26 7月, 2018 1 次提交
-
-
由 Stefan Ivic 提交于
Tackles the issue in #4025.
-
- 24 7月, 2018 2 次提交
-
-
由 S. Suzuki 提交于
I found mistake on readme
-
由 Tim Neutkens 提交于
Webpack 4, react-error-overlay, react-loadable (major)
-