1. Wrong import (line 5 `prefs.js`): [Port Guide 45: preferences](https://gjs.guide/extensions/upgrading/gnome-shell-45.html#preferences) 2. Avoid using unnecessary try and catch blocks. Please don't send the packages for reviews without testing them.

Uploaded v122. • Fixed prefs import to resource:///org/gnome/Shell/Extensions/js/extensions/prefs.js (per GNOME 45 guide). • Reduced unnecessary try/catch usage; now using guards and one minimal fallback in formatNow. • Settings created in enable() and nulled in disable() (kept from prior revision). • Flat zip; no compiled schemas. Thanks for the pointers.

If you are using the 45, you should include the compiled schemas too. Only 46+ packages won't need compiled schemas file.

Thanks for the quick follow-ups. A couple of points to reconcile: Compiled schemas on GNOME 45 According to the official GJS guide, since GNOME 44 the installer (E.G.O./gnome-extensions/Extension Manager) compiles schemas automatically, so extensions targeting 44+ should ship only the XML and avoid including schemas/gschemas.compiled. That’s explicit in the docs: “As of GNOME 44, settings schemas are compiled automatically…” (Preferences page). gjs.guide “If your extension is only supporting GNOME Shell 44 and later, you MUST only include the XML and avoid shipping gschemas.compiled.” (Porting to 44). gjs.guide There’s also a GNOME issue confirming this is intentional since 44. gitlab.gnome.org Given that, the requirement to ship a compiled schema for 45 appears to conflict with the published guidance. If E.G.O. has a 45-specific policy that differs from the GJS guide, could you link it? I’ll align both packaging and README accordingly. Pragmatics To keep review moving, I’ve uploaded v123 with schemas/gschemas.compiled included. Code remains ESM, uses this.getSettings() in both extension and prefs, initializes in enable() and nulls in disable(). Thanks—happy to adjust once there’s a definitive policy link for 45.