Marcus Williams

@khchan Sorry which problem are you referring as I mentioned a couple I was having.

@khchan I did it by sending the count in a header like this. ``` User.count().then(function(count) { User.find().paginate({ page: req.param('page'), limit: req.param('limit') }).then(function(users) { res.set('Access-Control-Expose-Headers', 'X-Total-Count'); res.set('X-Total-Count', count); res.ok(users); }); });...

OK I've worked out what the issue is. If a user already has a local account the only way they can currently link their account with a 3rd party provider...

I'm seeing some strange results too. Sometimes if I track myself in real time the page change shows, sometimes not. I just can't see a pattern that would give a...

I'm seeing the same behaviour as @shaunchander. Any idea when this might be fixed?

seeing the same, tried `AMPLIFY_NEXTJS_EXPERIMENTAL_TRACE=true` but this makes no difference on api routes

Netlify supports nextjs 12 https://github.com/netlify/netlify-plugin-nextjs/blob/main/docs/release-notes/v4.md so I would have thought it is possible

Think this would be a good addition as storing unnecessary backups could result in unnecessary costs.

> Still looking into this but it seems like the [exposeFetcher docs maybe incorrect](https://www.graphql-code-generator.com/plugins/typescript-react-query#usage-examples-3). Yes this fixed it for me

I'm having the same issue got 100's of pages and it only adds 13 random ones. Not sure what the issue is as it's detecting the urls just not adding...