Guneet Singh

@danielr18 Yeah I think I can do it. But currently I am stuck at how to change redux state using `next/link` API. Do you have a workaround?

Oh, I fixed it, that was a tiny configuration mistake. There was a wrong router reducer set.

Hi @danielr18 I looked further with the API and found that this repo does not give a porting option for `connected-react-router` users to `next` project as it not only lacks...

Thanks for the mention about `nextjs`v10 feature I can now the above example works like: ``` replace( `${paths.PRODUCTS}/[[...slug]]/`, `${paths.PRODUCTS}/${product.category}?${new URLSearchParams({id:id})}` ) ``` But I still see that replace function only...

Hi @danielr18 again, although I really wanted to contribute, this project is maintained in `TypeScript` and I know very less about it and I guess it would be a easy...

Please check the [PR](https://github.com/danielr18/connected-next-router/pull/60#issue-515359984).

Following @vincentleeuwen the below code did work for me, **though Facebook Pixel Helper still can't identify if my app has Pixel configured or not but the console logs proves it's...

LeakCanary as of v2.0+ can only be used as a debugImplementation in gradle and is not installed in release artifacts. Thats why you may not see these logs in production...

@consp1racy Then I would say I must test its release version as well before commenting on that. In the mean time I want to mention a similar leak I found...

> That's a totally different leak, just follow the trace. C'mon, if LeakCanary says it's a different leak then it is a different leak. Have some trust, it's the tool's...