ultimate-jekyll-manager 1.3.4 → 1.3.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -0
- package/dist/assets/js/libs/auth.js +14 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -14,6 +14,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
|
|
14
14
|
- `Fixed` for any bug fixes.
|
|
15
15
|
- `Security` in case of vulnerabilities.
|
|
16
16
|
|
|
17
|
+
---
|
|
18
|
+
## [1.3.5] - 2026-05-24
|
|
19
|
+
|
|
20
|
+
### Added
|
|
21
|
+
|
|
22
|
+
- **Diagnostic logging in `extractBlockingFunctionMessage()` (`src/assets/js/libs/auth.js`).** When BEM's `beforeCreate` rate limit (2 signups/day/IP) fires via Google OAuth redirect, the user just saw "Firebase: Error (auth/error-code:-47)" instead of the helpful "Unable to create account at this time. Please try again later." message. The 1.3.4 extraction handles the standard 400-with-`BLOCKING_FUNCTION_ERROR_RESPONSE` path, but the 503 path (Google's Identity Toolkit returns 503 directly with code -47, no `customData.serverResponse`) flows through to the generic `auth.code` branch. Added a `console.warn` that dumps the full error shape (code, message, customData, serverResponse) so the next failed signup attempt reveals exactly what Firebase delivers — then we can write a matching handler. Diagnostic ships first; fix follows in a subsequent version.
|
|
23
|
+
|
|
17
24
|
---
|
|
18
25
|
## [1.3.4] - 2026-05-22
|
|
19
26
|
|
|
@@ -802,6 +802,20 @@ export default function () {
|
|
|
802
802
|
//
|
|
803
803
|
// Returns just the inner message string, or null if nothing useful was found.
|
|
804
804
|
function extractBlockingFunctionMessage(error) {
|
|
805
|
+
// Diagnostic: dump the full shape of every error that lands here so we can
|
|
806
|
+
// see exactly what Firebase delivers when BEM's beforeCreate throws. The
|
|
807
|
+
// 503 path (Identity Toolkit returns 503 with code -47, no BLOCKING_FUNCTION
|
|
808
|
+
// wrapper) needs different handling than the 400 path.
|
|
809
|
+
console.warn('[Auth] extractBlockingFunctionMessage: error shape', {
|
|
810
|
+
code: error?.code,
|
|
811
|
+
message: error?.message,
|
|
812
|
+
name: error?.name,
|
|
813
|
+
hasCustomData: !!error?.customData,
|
|
814
|
+
hasServerResponse: !!error?.customData?.serverResponse,
|
|
815
|
+
serverResponse: error?.customData?.serverResponse,
|
|
816
|
+
fullError: error,
|
|
817
|
+
});
|
|
818
|
+
|
|
805
819
|
const raw = error?.customData?.serverResponse;
|
|
806
820
|
if (!raw) {
|
|
807
821
|
return null;
|