The built-in TypeScript fixture contains src/app.ts, src/styles.css, and README.md. The exact UTF-8-compatible payload is 199 bytes. The files contain 13 physical lines: 10 non-empty and 3 blank. SourceTally groups them as TypeScript, CSS, and Markdown, with one file in each language and extension row. No binary, excluded, oversize, or failed files are present.
TypeScript contributes 5 lines and 96 bytes
The app file has four non-empty lines and one blank line. It declares a title and a small greeting function. Its trailing newline terminates the fifth physical line and does not create an extra phantom line. This validates the same final-segment rule used for uploaded and remote streams.
CSS contributes 5 lines and 59 bytes
The stylesheet also has four non-empty lines and one blank line. Because physical counting ignores syntax, braces and declarations do not change the rule. The CSS row stays separate from TypeScript even though both belong to one frontend feature, making the table a composition view rather than a module-dependency model.
Markdown contributes 3 lines and 44 bytes
README.md contains a heading, one blank separator, and one sentence. Documentation is included because it is ordinary project text and the example does not enable an exclusion for it. If your question concerns application source only, use the language table to separate Markdown rather than silently subtracting documentation from every report.
Load the demo and verify all totals
Open the analyzer and choose TypeScript demo. The result must show 3 included files, 199 processed bytes, 13 physical lines, 10 non-empty lines, and 3 blank lines. The language and extension rows must sum to the same totals. If any number drifts, the fixture, browser calculation, SSR example, or test contract is inconsistent and the release should fail.