fix(style-editor): Now the style editor form is showed in UVE

[KevinDavilaDotCMS]

2026-04-28.17-35-27.mov

• Updated tests in and to use instead of for logging warnings.
• Adjusted the implementation in and to directly call for logging messages related to missing page queries and schema fetch failures.
• Removed unnecessary imports of from the test files to streamline the codebase.

This change enhances consistency in logging practices across the codebase.

This PR fixes: #35270

This PR fixes: #35270

[claude]

Claude finished @zJaaal's task in 1m 36s —— View job

---

PR Review

• Gather context
• Read changed files
• Analyze and post review

---

Core fix is correct. Removing the typeof window === 'undefined' guard in fetchStyleEditorSchemas (utils.ts:283–286) is the right call — the guard was silently preventing schema fetches in SSR/UVE contexts. The function already handles all failure cases gracefully, so this is safe.

The duplicate import removal in page.js is clean.

---

Issues worth flagging

1. Spy not restored — test leak (page-api.spec.ts:921)

const consolaWarnSpy = jest.spyOn(console, 'warn');
// ... assertions ...
// missing: consolaWarnSpy.mockRestore()

The spy is never torn down with mockRestore(), unlike every other spy introduced in this PR. It stays active and may suppress or misattribute console.warn calls in subsequent tests in this file. Fix this →

2. Stale test description (page-api.spec.ts:875)

it('should omit styleEditorSchemas and log debug when schema endpoint fails', ...

The implementation now logs at warn level, not debug. The description is misleading.

3. Inconsistent logging — partial consola migration

utils.ts now uses raw console.warn, but client.ts and page-api.ts still use consola. Since consola is still a runtime dep, nothing is gained from the partial switch. Either finish the migration or keep consola here too. The doc comment on fetchStyleEditorSchemas even says "failures are silently ignored", which console.warn contradicts (it emits to stderr in Node.js).

4. consola.debug → console.warn is a severity escalation

For generic/non-auth errors (network timeouts, unexpected 500s), what was a debug-level hint is now a warning. In SSR environments where the schema endpoint may be unavailable or unreachable, this will emit noisy warnings on every page render. If the intent is that these errors should be visible, that's fine — but it contradicts the "silently ignored" docstring and changes observable behavior.

---

No other issues.