This can basically be replaced by retrieveTransferredState() located in transfer_state.ts (we'll need to export it first).

I would expect this function to strip internal framework keys from packages/core/src/hydration/utils.ts : __nghData__ & __nghDeferData__ which are used for (incremental) hydration and don't have real meaning for developers.

nit: those aren't necessary anymore (since v19).

can also remove it, thank you.

Should replace this with a pure CSS solution (https://developer.mozilla.org/en-US/docs/Web/CSS/line-clamp) ?
(which would be applied to the DOM node that invokes this)

Nit: I think this should be | undefined since ng.ɵgetTransferState may not exist.

I know that currently if the protocol event data type and ɵgetTransferState return type diverge, we will get a compile-time error that they don't sufficiently overlap, but maybe it's safer to drop the assertion altogether?

Consider: Should we put a tooltip on the column (maybe with a ? icon) indicating that this is uncompressed size?

I know on Angular CLI bundle budgets a lot of people get confused whether we're listing disk size or transfer size, so it might be helpful to be explicit.

Actually we do provide an estimated transfer size based on simple formula. @clydin do you remember how that works? Maybe it would be worth including an estimated transfer size here?

Consider: Could we derive isLoading from whether either transferStateData and error have a value provided?

Consider: Should this include <code>? Would that be better for accessibility?

Consider: You can drop the _ destructures if you overwrite in a new object:

return {
  ...result,
  [TRANSFER_STATE_TOKEN_ID]: undefined,
  [TRANSFER_STATE_DEFER_BLOCKS_INFO]: undefined,
};

You might have to filter out keys with undefined values when consuming this. Alternatively, you can just delete the keys.

const transferState = retrieveTransferredState(doc, appId);
delete transferState[TRANSFER_STATE_TOKEN_ID];
delete transferState[TRANSFER_STATE_DEFER_BLOCKS_INFO];