forked from vercel/next.js
-
Notifications
You must be signed in to change notification settings - Fork 0
Master #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Master #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* implemented example for using redux with reselect and recompose * removed unused package * fixed linting issue * fixed linting issue
* docs: add algolia-react-instantsearch example * fix: style
* Update with-emotion to flush SSR styles on refresh * with-emtotion: remove @apply, use composes * fix env determination
This reduce the server boot-up time a lot. With a 2015 MacBook Pro, it went down from 1000ms to 200ms
* adds with react-i18next example * lint example code * remove unneeded .babelrc
This was causing the error “Failed prop type: Link: unknown props found: as in Link” when used with next-routes.
#2584) So, now we only use it for production.
…variant violation caused by bodyAttributes (#2587)
* Show webpack errors in all pages. When there's a webpack error that means HMR failed too. So, showing other pages won't makes sense since user can't edit them and get changes via HMR. That's why now we show the error on all pages. * Remove exact propType checks from the error component. When there's an error, something this check shows in the console. That means it could accept more props. Also this is not a public API. So, we don't want to do propType checks.
Sometimes, we've to reload the page for some changes. Even if so, we need to do it if that change is for the current page.
Add more HMR test cases
Add propTypes for replace and object support for href and as.
Next.js v4 requires React v16.
React v16 supports invalid DOM attributes now. ReactInjection and DOMProperty throws an error. Reference: #3152
* Add auto-publishing of new tags * Fix paste * Valid json * Remove now installation
* Add with-global-stylesheet-simple * Lint fix
Next 4 only works with React 16, so for this example to work we need an update.
* Updated dependencies related to Apollo and React. * Updated libs with Apollo 2 new set of modules. * Updated to Apollo 2 react integration modules. * Updated withData to separate apollo state from the app's state.
* Allow custom clientBootstrap entrypoint This allows for customization of the client global bootstrap. * Expose render event emitter to client * Include client entry point in npm package
* Add more example link for CSS preprocessor solution * Change deprecated link
Change file name format on folder lib like /examples/with-apollo and /examples/with-apollo-and-redux
`next@latest` instead of beta react 16
* example with-noscript use next@latest * fix : example/with-noscript react-dom/server usage Since the update to react ^16.0.0 react-dom import location has changed
* example with-redux-observable * fix styling with js standard-style
Add support for using withRouter as HOC with this example. Passing router context manually fixes this, based on, #2908 (comment)
* Adapt with-mobx example for with-mobx-state-tree * Remove unnecessary lastUpdate parameter to show off snapshot * update readme * make other.js more closely mimic index.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.