@gjsify/adwaita-fonts 0.41.0 → 0.42.0

package/400-italic.css

@@ -1,9 +1,13 @@
-/* Adwaita Sans — Italic 400 */
+/* Adwaita Sans — italic. Named `400` for the fontsource-style layout and because
+   that is the upstream file name; the TTF is a VARIABLE font (`fvar`: wght
+   100-900, opsz 14-32), so the face is declared over the whole range. Pinning
+   `font-weight: 400` here makes the engine synthesise every bolder weight —
+   measured, 700 and 800 came out pixel-identical. */
 /* Source: refs/adwaita-fonts (SIL OFL 1.1, GNOME contributors) */
 @font-face {
   font-family: 'Adwaita Sans';
   font-style: italic;
   font-display: swap;
-  font-weight: 400;
+  font-weight: 100 900;
   src: url('./files/adwaita-sans-400-italic.ttf') format('truetype');
 }

package/400.css

@@ -1,9 +1,13 @@
-/* Adwaita Sans — Regular 400 */
+/* Adwaita Sans — normal. Named `400` for the fontsource-style layout and because
+   that is the upstream file name; the TTF is a VARIABLE font (`fvar`: wght
+   100-900, opsz 14-32), so the face is declared over the whole range. Pinning
+   `font-weight: 400` here makes the engine synthesise every bolder weight —
+   measured, 700 and 800 came out pixel-identical. */
 /* Source: refs/adwaita-fonts (SIL OFL 1.1, GNOME contributors) */
 @font-face {
   font-family: 'Adwaita Sans';
   font-style: normal;
   font-display: swap;
-  font-weight: 400;
+  font-weight: 100 900;
   src: url('./files/adwaita-sans-400.ttf') format('truetype');
 }

package/README.md

@@ -1,6 +1,8 @@
 # @gjsify/adwaita-fonts
 
-Adwaita Sans TTF font files plus `@font-face` CSS (fontsource-style) for browser builds. Carries the GNOME/Libadwaita typographic identity to the web, sourced from the upstream Adwaita fonts project.
+Adwaita **Sans** TTF font files plus `@font-face` CSS (fontsource-style) for browser builds. Carries the GNOME/Libadwaita typographic identity to the web, sourced from the upstream Adwaita fonts project.
+
+Two faces ship: `adwaita-sans-400.ttf` (normal) and `adwaita-sans-400-italic.ttf` (italic). **No Adwaita Mono** — the upstream mono faces are 1.4–1.5 MB each and are not vendored here, so a `font-family: 'Adwaita Mono', …` stack resolves through this package only on a host where the typeface is installed system-wide (GNOME desktops, `adwaita-mono-fonts` on Fedora).
 
 Part of the [gjsify](https://github.com/gjsify/gjsify) project — Node.js and Web APIs for GJS (GNOME JavaScript).
 
@@ -17,22 +19,45 @@ yarn add @gjsify/adwaita-fonts
 ## Usage
 
 ```css
-/* Import the full @font-face declaration (weight 400, normal) */
+/* Both faces — the same two `./embedded` carries */
 @import '@gjsify/adwaita-fonts';
 
-/* Or import a specific weight variant directly */
+/* Or one face at a time */
 @import '@gjsify/adwaita-fonts/400.css';
 @import '@gjsify/adwaita-fonts/400-italic.css';
 ```
 
+Both TTFs are **variable** fonts (`fvar`: `wght 100-900`, `opsz 14-32`) despite
+the `400` in their upstream names, so each `@font-face` declares
+`font-weight: 100 900`. Pinning a single weight makes the browser synthesise
+every bolder one — measured in Firefox, 700 and 800 then render pixel-identical.
+
+Both forms above resolve `src: url('./files/adwaita-sans-400.ttf')` through the consuming CSS pipeline, which emits the TTF as an asset and serves it. That is the default and it is correct wherever such a pipeline exists — Vite, webpack, a plain `<link>`.
+
+### From JavaScript — use `./embedded`, never a side-effect import
+
 ```typescript
-// When used with a bundler that handles CSS imports
-import '@gjsify/adwaita-fonts';
+import { applyAdwaitaFonts } from '@gjsify/adwaita-fonts/embedded';
 
-// Then use the font family in CSS
-// font-family: 'Adwaita Sans', sans-serif;
+applyAdwaitaFonts(); // idempotent; injects a <style> with both faces
 ```
 
+**`import '@gjsify/adwaita-fonts';` from JavaScript does not register anything under a bundler that turns CSS into a string** — which includes `gjsify build --app browser` and `--app gjs`. The module it produces is `export default "<css>"`; a side-effect import of a module with no side effect is tree-shaken, and the build exits 0. Measured on 0.41.0: a probe entry whose only statement is that import builds to a **0-byte bundle with zero `@font-face`**. And even when the string is kept (`import css from …`), its relative `url()` resolves against the document, while a `--app browser` build emits one file and no assets — so the rule parses and the face 404s.
+
+`./embedded` is the form that survives both: every `src:` is a `data:` URI, and it is a **value** import, which a bundler cannot silently discard.
+
+### The cost, and why it is opt-in
+
+These are unsubsetted desktop TTFs, not web fonts. Base64 is 4/3 of the payload:
+
+| | bytes | gzip -9 |
+|---|---:|---:|
+| `@gjsify/adwaita-web` stylesheet | 190 731 | 25 891 |
+| `+` sans 400 inlined | 1 363 795 | 594 177 |
+| `+` sans 400 + italic inlined | 2 577 599 | 1 205 683 |
+
+So `@gjsify/adwaita-web` does **not** import `./embedded` from its root entry — ~600 KB gzip for a typeface that is installed system-wide on the platform it targets is the wrong default. Opt in per app, with the one line above. Importing only `ADWAITA_SANS_400_CSS` (and injecting it yourself) leaves the italic face tree-shakeable.
+
 ## License
 
 OFL-1.1

package/index.css

@@ -1 +1,7 @@
+/* Both faces this package ships, so the `.` export and `./embedded` agree on what
+   "Adwaita Sans" means. It used to be `400.css` alone: a CSS-pipeline consumer
+   following the documented route got no italic and no diagnostic, while
+   `applyAdwaitaFonts()` registered two — an asymmetry nothing stated. Import
+   `./400.css` directly for the normal face only. */
 @import './400.css';
+@import './400-italic.css';

package/index.d.ts

@@ -1,3 +1,8 @@
-// Type declaration for @gjsify/adwaita-fonts CSS side-effect import.
-// Importing this package registers @font-face declarations for Adwaita Sans.
+// The `.` export of this package is a STYLESHEET (`index.css`), for a CSS
+// pipeline that resolves `url('./files/*.ttf')` — Vite, webpack, a `<link>`,
+// Astro's `customCss`. Importing it from JavaScript registers nothing: under
+// `gjsify build --app browser|gjs` the css-as-string plugin turns it into
+// `export default "<css>"`, and a side-effect import of a module with no side
+// effect is tree-shaken away at exit 0. From JS use `./embedded`, whose faces
+// are `data:` URIs behind a VALUE import (`applyAdwaitaFonts()`).
 export {};