* pass down getInitialProps ctx to ComposedComponent
* pass apollo client instance directly to getDataFromTree instead of through the ApolloProvider wrapper.
* Avoid redundant empty serverState initialization (It's always initialized)
* remove global npm install of create-next-app
* add npx to create-next-app command in examples
* add bash to shell snippets
* add yarn create to next-app command in examples
* fix READMEs named with lowercase
* change READMEs to use UPPERCASE
* FIX deploy with-firebase-hosting
* add npm run command in place of yarn in firebase.json predeploy hooks
* Change yarn with npm
* firebase-hosting example: Add warning in examples README
* firebase-hosting example: clarify warning language
* firebase-hosting example: remove the warning and upgrade to canary
* firebase-hosting example: actually upgrade pkg.json
- simplify pages by introducing withI18next hoc
- add Trans component example
- replace <div> with <p> in demo components to make text on pages easier to read
German translation by @marinaroot
* Next.js v5 update, _error & _document bugs fixes
* document clean script
* remove old build artefact
* add babelrc
* reset next.js version to 'latest' from '^5.0.0'
* typo in readme
* format code
* remove _files as they were a fix for a solved, but unreleased problem
* [example] with-apollo-and-redux-saga
- Using Apollo to get GraphQL Data? Dope.
- Using Redux Saga to do other stuff outside of that? Cool.
- Nary the two shall meet? Most likely. 😀️
This is a breakout of #3463 where we were combining Apollo and Redux.
This may not be an example that gets a PR.
Why? Well, the examples are meant to pick and choose and combine
yourself. At least I believe, and this is basically a combination of two
examples (`with-apollo` and `with-redux-saga`) with some reworking.
**pages/**:
`index`: withReduxSaga()
`about`: ()
`blog/index`: withReduxSaga(withApollo())
`blog/entry`: withApollo()
* [refactor] fix lint (again), remove superfluous calls
* [fix] package.json: with-apollo-and-redux-saga
Updated the `name` and made sure `es6-promise` was in dependencies
* [refactor] remove semi-colons in clock/sagas
* [refactor] remove old migration code
* Add custom-server-typescript example (see #3694)
* Fix linting errors in custom-server-typescript
* Provide proper arguments to ts-node.
* Fix import and fix all linting errors.
* Use import in server as well.
* Update nodemon.json
* 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)
* with emotion example - hoist styles out of the index page component (#3821)
* Use indexOf instead of startsWith (#3758)
* Use indexOf instead of startsWith
This fixes an IE11 regression, see #3755
* Lint the code
* #3700 Add examples for next-sass
* #3700 Use React.Fragments and more
* Fix#3700 remove some keys to make more clear
* Fix#3700, change to without-css-modules
* Replace PageWrapper with _document for more concise code. #3700
Got this fix from issue #2302. Libraries like `font-awesome` are pretty common. Indicating how to get them to work should be indicated in the `README.md` (if not added to the example)
* move imports into files using lettable operators, remove rxjs-library
* refactor to be more in keeping with redux conventions
from the single reducer.js, I split the functionality into actionTypes
(actionTypes.js), actions (actions.js), and epics (epics.js). Most of
the fetching should be done in an epic, but that requires introducing a
new action and so was
better in a separate commit.
* switch to fetching on the front-end via an epic
The fetching previously was triggered using an api call that had side
effects, but was triggered from inside of an epic and was not an action.
Now calls on the front-end all of the api calls are occuring via an
action through fetchCharacterEpic. This does not remove the api.js file
as I have not yet been able to get the epic to trigger correctly on the
server-side, thus the api.fetchCharacter call is awaited in
getInitialProps for initialising the state serverSide.
* remove need for the serverSide api by directly handling the dispatch
This still seems to be an incomplete solution to the problem as it
circumvents the standard redux event flow on the serverside. However, it
does obey the spirit of the redux event flow (as it passes an Observable
of an action into the epic to then trigger other actions). Additionally,
this removes the problem of code duplication.
* update README.md and move lib/ to redux/
* Fix linting
* Add example on how to pass data through js api during SSR
Requested in #1117
* Use content negotiation instead of a separate route
* Codereview feedback
* 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
* next export will expand symlinks now
* Make sure next export doesn't includes _document.js in windows
* avoid a client side not found page when navigating to a custom route
* [fix] apollo-redux: Separate out entire example #3463
Apollo and Redux are completely separate ways of managing state. This example serves as a conduit if you were using Apollo 1.X with Redux, and are migrating to Apollo 2.x, however, you have chosen not to manage your entire application state within Apollo (`apollo-link-state`).
There is no "withData" function that allows you to call either/or. You must call "withRedux" and/or "withApollo" on your Component. They can be combined in the example at `index.js` or remain separate as seen in `apollo.js` and `redux.js`.
Going forward, this example may go the way of the dodo.
* [chore] reformat code to match next syntax
Localize prettier sometimes has a mind of its own. 😄️
* Fix linting
This patch adds an example of a Next.js app using analytics. A custom
document injects the [Segment](https://segment.com) bootstrapping
snippet into the `<head>`, allowing "page" and "track" calls to be made.
An issue came up in CNA asking how we handle this in our apps (see
https://github.com/segmentio/create-next-app/issues/24), so I figure an
"official example" could help.
NOTE: I am affiliated with Segment.
* Speed up next build
* Document webpack config
* Speed up next build
* Remove comment
* Add comment
* Clean up rules
* Add comments
* Run in parallel
* Push plugins seperately
* Create a new chunk for react
* Don’t uglify react since it’s already uglified. Move react to commons in development
* Use the minified version directly
* Re-add globpattern
* Move loaders into a separate variable
* Add comment linking to Dan’s explanation
* Remove dot
* Add universal webpack
* Initial dev support
* Fix linting
* Add changes from Arunoda's work
* Made next dev works.
But super slow and no HMR support.
* Fix client side hot reload
* Server side hmr
* Only in dev
* Add on-demand-entries client + hot-middleware
* Add .babelrc support
* Speed up on demand entries by running in parallel
* Serve static generated files
* Add missing config in dev
* Add sass support
* Add support for .map
* Add cssloader config and fix .jsx support
* Rename
* use same defaults as css-loader. Fix linting
* Add NoEmitErrorsPlugin
* Add clientBootstrap
* Use webpackhotmiddleware on the multi compiler
* alpha.3
* Use babel 16.2.x
* Fix reloading after error
* Remove comment
* Release 5.0.0-univeral-alpha.1
* Remove check for React 16
* Release 5.0.0-universal-alpha.2
* React hot loader v4
* Use our static file rendering machanism to serve pages.
This should work well since the file path for a page is predictable.
* Release 5.0.0-universal-alpha.3
* Remove optional loaders
* Release 5.0.0-universal-alpha.4
* Remove clientBootstrap
* Remove renderScript
* Make sure pages bundles are served correctly
* Remove unused import
* Revert to using the same code as canary
* Fix hot loader
* Release 5.0.0-universal-alpha.5
* Check if externals dir exist before applying config
* Add typescript support
* Add support for transpiling certain packages in node_modules
Thanks to @giuseppeg’s work in https://github.com/zeit/next.js/pull/3319
* Add BABEL_DISABLE_CACHE support
* Make sourcemaps in production opt-in
* Revert "Add support for transpiling certain packages in node_modules"
This reverts commit d4b1d9babfb4b9ed4f4b12d56d52dee233e862da.
In favor of a better api around this.
* Support typescript through next.config.js
* Remove comments
* Bring back commons.js calculation
* Remove unused dependencies
* Move base.config.js to webpack.js
* Make sure to only invalidate webpackDevMiddleware one after other.
* Allow babel-loder caching by default.
* Add comment about preact support
* Bring back buildir replace
* Remove obsolete plugin
* Remove build replace, speed up build
* Resolve page entries like pages/day/index.js to pages/day.js
* Add componentDidCatch back
* Compile to bundles
* Use config.distDir everywhere
* Make sure the file is an array
* Remove console.log
* Apply optimization to uglifyjs
* Add comment pointing to source
* Create entries the same way in dev and production
* Remove unused and broken pagesGlobPattern
* day/index.js is automatically turned into day.js at build time
* Remove poweredByHeader option
* Load pages with the correct path.
* Release 5.0.0-universal-alpha.6
* Make sure react-dom/server can be overwritten by module-alias
* Only add react-hot-loader babel plugin in dev
* Release 5.0.0-universal-alpha.7
* Revert tests
* Release 5.0.0-universal-alpha.10
* Make sure next/head is working properly.
* Add wepack alias for 'next' back.
* Make sure overriding className in next/head works
* Alias react too
* Add missing r
* Fragment fallback has to wrap the children
* Use min.js
* Remove css.js
* Remove wallaby.js
* Release 5.0.0-universal-alpha.11
* Resolve relative to workdir instead of next
* Make sure we touch the right file
* Resolve next modules
* Remove dotjsx removal plugins since we use webpack on the server
* Revert "Resolve relative to workdir instead of next"
This reverts commit a13f3e4ab565df9e2c9a3dfc8eb4009c0c2e02ed.
* Externalize any locally loaded module lives outside of app dir.
* Remove server aliases
* Check node_modules reliably
* Add symlink to next for tests
* Make sure dynamic imports work locally.
This is why we need it: b545b519b2/lib/MainTemplate.js (L68)
We need to have the finally clause in the above in __webpack_require__.
webpack output option strictModuleExceptionHandling does that.
* dynmaic -> dynamic
* Remove webpack-node-externals
* Make sure dynamic imports support SSR.
* Remove css support in favor of next-css
* Make sure we load path from `/` since it’s included in the path matching
* Catch when ensurepage couldn’t be fulfilled for `.js.map`
* Register require cache flusher for both client and server
* Add comment explaining this is to facilitate hot reloading
* Only load module when needed
* Remove unused modules
* Release 5.0.0-universal-alpha.12
* Only log the `found babel` message once
* Make sure ondemand entries working correctly.
Now we are just using a single instance of OnDemandEntryHandler.
* Better sourcemaps
* Release 5.0.0-universal-alpha.13
* Lock uglify version to 1.1.6
* Release 5.0.0-universal-alpha.14
* Fix a typo.
* Introduce multi-zones support for mircofrontends
* Add section on css
* [refactor] with-apollo-and-redux: 2.0.0
- This ports over `with-apollo` (w/ recent `withRouter` fix and addition
for Post) along with implementing `apollo-cache-redux` #3463
- The `redux` side of things is lacking (it is the *same* as the
original example)
- Created a `routes.js` for use on Server and Client Side (to expand the
PostList functionality)
- SSR is maintained
- Redid the "PostVote" a bit... sorry. 😬️
Possible todo(s):
- Add in API and Clock Examples from `with-redux` to show Apollo and
Redux working together a bit more
- redux-saga (I personally use this, may be too opinionated for the base
example though)
Packages updated:
- apollo-cache-redux
- apollo-client-preset
- graphql
- graphql-anywhere
- graphql-tag
- isomorphic-unfetch
- next-routes
- prop-types
- react
- react-apollo
- react-dom
- redux
* [refactor] fix linting issues
When I run `yarn lint` explicitly these were caught, but not doing a
build proper. Apologies on that!
* [chore] 📦️ package.json: like other examples
* [refactor] +apollo-cache-inmemory, -apollo-cache-redux
Separation of Apollo and Redux. 😄️
We could stand to use a few actual examples of Redux, though this is a
good starting block.
Some other code cleanup as well.
* Always fetch pages with '.js' extention from client side.
* Load error page always from _error.js rather _error/index.js
* Load pages from page.js instead of page/index.js from the client for static exports.
* Update index.js
* Simplify the path re-write logic in the webpack pages-plugin.
* Pulled encoding to top of head (#3214)
* Remove next.d.ts to use @types/next (#3297)
* Add with-mobx-state-tree example (#3179)
* 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
* Upgrade styled-jsx to v2.2.1
Includes some bug fixes.
* Fix linting
The serverState variable definition did not include the data node, which
may cause parsing errors on the client-side.
- add data: { } on line 23 within the apollo: { } object
* 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
* Updated for Apollo 2.0
* Updated for commit: ccb188a
* Simplified serverState
Updated with danistefanovic's comment. Looks better.
* Revert "Simplified serverState"
This reverts commit 1b543a35909dcfe401c753cb2f71760180087057.
* Simplified server
Updated with Statedanistefanovic's comment.
getToken is now deprecated, you'll get the following message if using the previous code:
firebase.User.prototype.getToken is deprecated. Please use firebase.User.prototype.getIdToken instead.
Prior to react-apollo 2.0 createNetworkInterface accepted the credentials option in {opt: {credentials: 'policy'}}. HttpLink accepts it as {credentials: 'policy'}.
This has never been working, we based our intl + locale lookups out of this example and found out when translations wasn't working on page transitions due to the fact that messages gets set to undefined because its trying to destruct in the incorrect level
* 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
* [fix] with-apollo: Cannot read property 'data'
When we create the initial serverState, we need to create the
eventual construct of the Apollo Data to reside within
Later in the constructor this allows for the initApollo to either
be generated from SSR, or to init from scratch.
Fixes
> Cannot read property 'data' of undefined
> TypeError: Cannot read property 'data' of undefined
* [refactor] with-apollo: reduce init `serverState`
No need to explicitly set `data` as empty.
This trims up 4 lines. 😀️
* 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.
* 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.
* [chore] styled-jsx-plugin-sass@0.2.0, show dynamic
styled-jsx-plugin-sass had an update that now allows for sass and
dynamic to live together.
This updates that package and updates the example slightly to show how.
* [fix] errant space in styled-jsx-scss example
* Make styled-jsx configurable
* Add styled-jsx-plugin-postcss example
* Add styled-jsx 2.1.0 with plugins support
* Move examples around and add description
* Add link to new example
* Update babel-preset.js
As './dist/server/build/babel/preset' now return a function, in this example we need to first call the function and after that replace styled-jsx
* linting issues solved
* don't fetch messages server-side if user is not found
Currently, the component always fetch everything under '/messages' even if the user is not authenticated on the server side. Update it to not fetch if the user is not found as a better example on handling.
* fix lint error
* emotion v8 + adjustments for breaking changes
* Corrected versioning
* Take hydrate from 'react-emotion'
I was actually wondering that, but haven't seen hydrate in the medium post (even though you pointed out that react-emotion exports all of emotion and I've seen it in source) and didn't want to risk it for the off chance that it *should* be imported directly from emotion for some reason :D
* Configurable opts for babel-preset-env + babel-plugin-transform-runtime
This adds `preset-env` and `transform-runtime` options to the
`next/babel` Babel preset, which are then passed through to those
presets and transforms. This allows configuration to keep next.js
from the default 'maximum' transform, and instead use built-in
implementations of globals, classes, async, and other commonly-supported
features.
Fixes#2989
* Use spread notation instead of Object.assign
* Git ignore with-reasonml/lib folder
The lib folder contains code generated by BuckleScript, it shouldn't be
versioned.
* Fix, case sensitive paths
Next.js use case-sensitive-paths-webpack-plugin and BuckleScript tries
to maintain the filename case.
* Refactor, use a .babelrc file instead of a babel config in package.json
This is the official recommended way in Next.js
* Enable way, way, waaaay nicer error messages!
Adds `"bsc-flags": ["-bs-super-errors"]` to the bsconfig.json file.
https://reasonml.github.io/community/blog/#way-way-waaaay-nicer-error-messages
* Fix npm scripts & use concurrently to run bsb & next in parallel for dev
* Upgrade bs-platform
* Replace statefulComponent with new reducerComponent
https://github.com/reasonml/reason-react/blob/master/HISTORY.md#024
* Upgrade with-reasonml example to next.js 3
* Define dependencies & NPM stuff for the example
* Setup Babel preset
* Add sources of working version of example
* Indicate ajax loading state
* Add readme file
* Remove unneeded .babelrc
* Corrected dependencies for the preact example. Require react and react-dom
* Corrected dependencies for the inferno example. Require react and react-dom
* Add withRoute HOC
Rebased (squashed)
- removed routerToProps
- updated hoist-non-react-statics
- improved propTypes
* Expose the whole Router instead of the route.
* Make the example simple.
* Update examples and the readme.
* Add a test case.
* Add examples/with-redux-code-splitting. (#2721)
* #1757 Relay Modern Example (#2696)
* Add ReasonML example (#2640)
* Add ReasonML example
* Add a gitignore specifically for the reasonml example
* Allow custom className for <Main /> (#2802)
* 3.0.2
* Remove beta information from the README.
* 3.0.3
* Remove unnecessary lookup in example with emotion (#2731)
* Document SCSS/Less (#2742)
* Document SCSS/Less
* Add missing word
* Add docs for examples dir
* Add extra example
* uppercase J
* Add with pkg example (#2751)
* Add custom server micro example (#2750)
* Ease running multiple examples at the same time with process.env.PORT (#2753)
* Add line-height rule for error page h2 (#2761)
* Add support for fetching multiple translation files (#2743)
* Add support for fetching multiple translation files
* Cleanup
* Clear missed interval (#2611)
* clear missed interval
* remove trailing whitespace
* Relay Modern Example (#1757) (#2773)
* Simplification of Relay Modern Example (#1757) (#2776)
* Use deterministic names for dynamic import (#2788)
* Always use the same name for the same dynamic import.
* Add unit tests for the modulePath generation.
* Allow tests to run correctly on Windows.
* Make the chunk name a bit pretty.
* Fix tests to run on Windows.
* 3.0.4
* Revert "Make the chunk name a bit pretty." (#2792)
This reverts commit 0c9e8cf2271955e74ab9f752b5869b98c1dc60f9.
* 3.0.5
* Use _ as the divider for dynamic import name splitter. (#2793)
Using - gives us some weird webpack errors.
* 3.0.6
* next/dynamic Error Message Tweaks (#2798)
* Fixed issue (#2804)
https://github.com/zeit/next.js/issues/2800
* docs(material-ui): move the source code to Material-UI repository (#2808)
* Add Electron usage example
* Remove the deploy part
* Only allow GET request to our HTTP server
* Only allow request from an electron app (checking the user agent)
* Add warning about the local HTTP server
* Update package.json
* Update example to use Next.js v3
* Added required package.json fields with placeholders
* Use next:// file protocol to open internal built files
* Create next.config.js
* Update set-menu.js
* Update example to merge it with electron-next-skeleton ideas
* Rename Firebase Auth example
* Update gitignore to include npm5 lockfile
* Cloud Function
* Add Next app with two pages to demonstrate navigation
* Add Firebase Hosting and configuration to Host & Deploy
* Fix errors in rename for firebase-auth example
* Recommend pkg managers with caches for better perf
* Update with-firebase-hosting example
Fix code
* Update with-firebase-hosting example
Fix npm scripts and package.json files
* Update with-firebase-hosting example
Update README & install scripts
* Update with-firebase-hosting example
Update example package name
* Update with-firebase-hosting example
Fix to use single-quotes
* Update with-firebase-hosting example
VSCode did not like single-quotes! Sorry
* Fix gitignore file
By creating an intermediary component (with the HOC)
we save some React rendering logic.
That's also addressing an issue with JssProvider (react-jss)
that generate a new index at each render.
* Added react and react-dom dependencies
Added missing `react` and `react-dom` dependencies which are required by next.js
* Moved react & react-dom to dependencies
Moved react & react-dom to dependencies from devDependencies
* Fixed: css-modules reload files styles.css.json.
* update: disable uglify for next build.
add: require('fs') for next build.
add: disable uglify on next.config.js for next build.
* Fix linting errors
* feat: Add react-uwp examples
* fix: remove log from ThemeWrapper
* feat: Add README.md
* fix: Fixed right version
* fix: Use JavaScript Standard Style
* fix: Fixed wrong next version
* Layout ground works for next/async
* Implement the Dynamic Bundle feature.
* Add some test cases.
* Update README.
* Implement props aware dynamic bundle API.
* Update tests and README.
* Add a test case for React Context support.
With a hard coded address on the client, the app no longer works when deploying, which is annoying since there's a handy 'deploy now' button on the readme.
By removing the hard coded address socket.io will connect to the location host automatically so it works both on development and production.
