signinwith 1.0.5 → 1.0.7

package/index.js

@@ -34,10 +34,10 @@ export const verifySigninDiscord = async (config, verificationData) => {
 	return profile.email ? { success: true, email: profile.email } : { success: false, error: 'Email not available from Discord' };
 };
 
-export default verifySignin = async (services, service, verificationData) => {
+export default async function verifySignin (services, service, verificationData) {
 	try {
 		if (services.google && service === 'google') return await verifySigninGoogle(services.google, verificationData);
-		if (services.meta && service === 'meta') return await verifySigninMeta(services.meta, verificationData);
+		if (services.facebook && service === 'facebook') return await verifySigninMeta(services.facebook, verificationData);
 		if (services.apple && service === 'apple') return await verifySigninApple(services.apple, verificationData);
 		if (services.discord && service === 'discord') return await verifySigninDiscord(services.discord, verificationData);
 		return { success: false, error: 'Unsupported service' };

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "signinwith",
-	"version": "1.0.5",
+	"version": "1.0.7",
 	"description": "Simple and straightforward library for sign in / sign up with thirdparty oAuth services like Google, Meta, Apple, Discord...",
 	"main": "index.js",
 	"scripts": {

package/readme.md

@@ -247,4 +247,9 @@ For Discord and Apple, the `redirectUri` in the frontend configuration should po
 </html>
 ```
 
-This HTML file extracts the authorization code (or error) from the URL hash and sends it back to the main window using `postMessage`.  The main application needs to listen for this message and then proceed with the backend verification.  This approach is necessary because Discord's OAuth flow, when initiated in a popup, requires a way to pass the authorization code back to the originating window.
+This HTML file extracts the authorization code (or error) from the URL hash and sends it back to the main window using `postMessage`.  The main application needs to listen for this message and then proceed with the backend verification.  This approach is necessary because Discord's OAuth flow, when initiated in a popup, requires a way to pass the authorization code back to the originating window.
+
+Note: you can import this page as a string (to then return it as a response from your server) via:
+```javascript
+import htmlContent from 'signinwith/redirect-oauth.html?raw';
+```