feat(provider): Add instagram

[PolMrt]

Add Instagram as a provider.

Note that I've add node-fetch npm package because the Instagram api only returns some informations such as username, id, account_type. I've add a request to Instagram public api (https://www.instagram.com/instagram/?__a=1) which, strangely, returns more informations such as full name and profile pictures (this works for public and private accounts).

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/o3fipdopn
✅ Preview: https://next-auth-git-main.nextauthjs.vercel.app

[ndom91]

@PolMrt next.js ships with an isomorphic version of fetch since 9.4+.

Take a look at this example for usage:

https://github.com/nextauthjs/next-auth/blob/canary/src/client/index.js

It's wrapped up in a custom function _fetchData located towards the bottom of the file. Can you please use that instead of adding a new dependency? Otherwise it looks good, thanks! 🎉

[PolMrt]

Thanks I'll update that. But I tried to use this "public API" for another project and it seems to not be usable as an API, sometimes it will redirects you to a login page if you haven't logged to Insta with your ip in a while... So I don't think this is the best approach.

Would it be okay if we only stuck with the username ? Or should we still use this unstable API and return no email, picture, name (as the Instagram API don't return that kind of information for non-business account) if there's a redirection ?

[balazsorban44]

I added some suggestions to eliminate node-fetch. Could you please check out if this still works for you locally?

[PolMrt]

Thanks for your help @balazsorban44. Everything seem to be fine, gonna try this tomorrow morning !

[balazsorban44]

Suggested change

	logger.error("PROFILE_FETCH_ERROR", error)
	logger.error("PROFILE_FETCH_ERROR", error)
	return {
	id: profile.id,
	name: profile.username
	}

Maybe return the profile id and username in case of an error also?

[balazsorban44]

@PolMrt I added another suggestion. Also, could you make sure that there are no linting errors, and could you report back if you have tested these changes locally successfully? Thank you!

[PolMrt]

I don't think we're in the good path right now. Let me explain :

My initial idea (using Instagram public api) was working because I tried it on localhost. Next's server side and client side were using the same IP. So it was always working because of it. But when it will be used in production, this would never work, not even once since the IP of the server has never been used in Instagram.

I think we should just return user id and username, nothing else. Implementing a solution that might works some time but not most of the time will be very confusing for developers.

We should say in the doc that only the username is returned and maybe add a second Instagram provider for business account using the API reserved to that kind of account (which returns a lot more of informations).

Please tell me if that sounds good to you and I'll update the PR.

[balazsorban44]

Sorry for the delay. So I found this documentation: https://developers.facebook.com/docs/instagram-basic-display-api/reference/user

if I understand it correctly, you simply don't have the option to get the user's email?! 😕 Very strange from Instagram.

I'm not sure how to proceed, cc @iaincollins

[github-actions]

🎉 This issue has been resolved in version 3.8.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 4.0.0-next.5 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀