- 03 Sep, 2018 7 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
Fixes #5021
-
Don Alvarez authored
Pulling out a few core points from the readme... This example builds from /src into /dist, managing the different expectations of express.js (es5, commonjs) and next.js (es6) by using a pair of tsconfig.json files, both of which are run by `npm run build-ts` or any of the other npm targets. Hot module reloading is largely but not completely wired up (nodemon is watching /dist but tsc isn't set up to watch /src and transpile changes in /src to /dist automatically (that's mainly because I wasn't sure how to start both nodemon and a pair of tsc watchers and be confident all would get shut down when the user killed dev mode). The readme suggests running `npm run build-ts` manually in another window to push changes from /src into /dev and on into the browser. tslint is also wired up via `npm run tslint`
-
Tim Neutkens authored
## Minor changes When `NODE_ENV=test` is used we'll now apply the `'auto'` configuration for modules transformation. Which causes Babel to check if the current environment needs to be transformed or not. In practice this means that the following `.babelrc` is not needed anymore: **OLD**: ```json { "env": { "development": { "presets": ["next/babel"] }, "production": { "presets": ["next/babel"] }, "test": { "presets": [["next/babel", { "preset-env": { "modules": "commonjs" } }]] } } } ``` **NEW**: ``` { "presets": ["next/babel"] } ``` ## Patches `@babel/preset-react` has a `development` option that automatically applies a development-time plugin we manually applied before (`@babel/plugin-transform-react-jsx-source`). It also adds another development-time plugin that is said to make debugging/errors clearer: `@babel/plugin-transform-react-jsx-self` which we didn't apply before. Overall this means we can take advantage of preset-react to provide these plugins. -
George Pantazis authored
Currently, using `as` will cause the router to think the URL is not changing in the case where you're re-rendering the same page with a different route. This would most likely be an issue for custom servers which are using shallow routing. This should be an invisible change for non-custom-server users, since `as` is defaulted to `url` if not set. This should resolve #3065.
-
Tim Neutkens authored
-
Tim Neutkens authored
-
- 02 Sep, 2018 10 commits
-
-
Bertrand Marron authored
* Keep chunks filenames in production mode * Add test for new `[name]` behavior * Rename static/dll to static/development/dll
-
Adam Lane authored
The original example fails to compile on my windows machine but updating bs-platform fixes that. Depending on bs-next causes example to fail (package compiled with old incompatible version of bs-platform) so I have included it in a bindings directory where it can serve as an example of reason bindings. Sources have been migrated to the latest reason-react.
-
Tim Neutkens authored
-
Ivan Starkov authored
react-intl does not work otherwise
-
Tim Neutkens authored
-
Tim Neutkens authored
Fixes #5038 The problem with `constructor` is that it doesn't have `context` yet when being called. It's also considered unsafe to add a side-effect on constructor except when server-rendering
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
- 01 Sep, 2018 1 commit
-
-
Tim Neutkens authored
-
- 31 Aug, 2018 3 commits
-
-
Tim Neutkens authored
This fixes an issue with styles jumping around when using `transition: all`
-
Henrik Wenz authored
## Issue Currently react-error-overlays launch-editor functionality doesn’t work because the module paths are in the wrong format. ## Todo - [x] Keep source-maps enabled ## Related https://github.com/zeit/next.js/pull/4979
-
Popuguy authored
Babel loader v8 now for babel v7 other update fix bugs and performance improvements
-
- 30 Aug, 2018 8 commits
-
-
Vince Picone authored
Some really nasty Internal Server errors come as a result of not having the correct module name here.
-
Daniel Reinoso authored
Fixes #5052. Example was using babel 6.
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
This fixes intermittent `loading...` on some requests which surfaced on zeit.co when upgrading
-
Tim Neutkens authored
-
- 29 Aug, 2018 1 commit
-
-
Nikhil Fadnis authored
In my use case, the client pings are failing since the requests do not send basic auth credentials right now. This change was made in https://github.com/zeit/next.js/pull/2509 I am not sure why it was undone as a part of https://github.com/zeit/next.js/pull/3578 Can someone explain why? Thanks.
-
- 28 Aug, 2018 4 commits
-
-
Tim Neutkens authored
-
Faris Abusada authored
😬 ... https://w3c.github.io/preload/ -
Tim Neutkens authored
-
-
- 27 Aug, 2018 2 commits
-
-
Tomáš Witek authored
It looks like we don't need the `_document.js` file anymore. Is that correct?
-
Kyle Holmberg authored
Resolves #5035 Thanks a billion to @timneutkens for holding my hand
-
- 25 Aug, 2018 4 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
* Remove UNSAFE_componentWillMount * Remove UNSAFE_componentWillReceiveProps from lifecycle
-
Michael Fix authored
~I am not sure if this is a valid fix yet, but I was going to let CI run the tests for me. I'll close and look into it if the build fails.~ Let me know if this will cause issues, but I don't think it should. The React docs recommends moving `componentWillMount` logic into the constructor
-
HaNdTriX authored
* Add test of default head. * Remove duplicate next-head (followup #5026)
-