You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use unistore with next.js. It works great until a page has a static method getInitialProps that needs to be called.
The way next.js works is that there is an _app.js file that acts as a parent container and loads the page as a child.
That parent is responsible for calling the getInitialProps of the child page. When I wrap my page with connect()(Page); the parent is not able to call getInitialProps anymore as the component returns the new component created by the connect method. Just wondering if anyone has any idea on how to handle this?
//_app.js
import React from "react";
import App, { Container } from "next/app";
import createStore from "unistore";
import { Provider } from "unistore/react";
let store = createStore({ count: 0 });
class MyApp extends App {
static async getInitialProps({ Component, ctx }) {
let pageProps = {};
//Never gets triggered when page is wrapped in connect()
if (Component.getInitialProps) {
pageProps = await Component.getInitialProps(ctx);
}
return {
...pageProps
};
}
render() {
const { Component, pageProps } = this.props
return (
<Provider store={store}>
<Container>
<Component {...pageProps} />
</Container>
</Provider>
);
}
}
export default MyApp;
//pages/index.js
import Link from "next/link";
import { connect } from "unistore/react";
const Index = props => {
return (
<div>
Hello World .. {props.count}
<Link href="/about">
<a>Abouts</a>
</Link>
</div>
);
};
Index.getInitialProps = () => {
console.log(" CALL THIS");
return {
hello: 'bye'
}
}
export default connect(['count'])(Index);
The text was updated successfully, but these errors were encountered:
Hooks-based integrations for React and Preact should be coming shortly, which would be a nice fix for this since they don't wrap your component at all.
Hi,
I am trying to use unistore with next.js. It works great until a page has a static method getInitialProps that needs to be called.
The way next.js works is that there is an _app.js file that acts as a parent container and loads the page as a child.
That parent is responsible for calling the getInitialProps of the child page. When I wrap my page with connect()(Page); the parent is not able to call getInitialProps anymore as the component returns the new component created by the connect method. Just wondering if anyone has any idea on how to handle this?
The text was updated successfully, but these errors were encountered: