Codesandbox bundling seems to just drop the initializer altogether. Prior history of causing issues. Generally declared as a feature to avoid because it confuses tooling all around. While I understand the appeal of having a name refer to both a type and a value at the same time, because of aforementioned reasons I would like to ban all usage of the namespace feature.

How do you feel about any of the following patterns:

export type PinnedRows = {
  top: RowEntry[];
  bottom: RowEntry[];
};
export const PINNED_ROWS = {
  empty: { top: [], bottom: [] } as PinnedRows
}
// or
export const PINNED_ROWS = {
  EMPTY: { top: [], bottom: [] } as PinnedRows
}
// or
export const PinnedRowsValues = {
  EMPTY: { top: [], bottom: [] } as PinnedRows
}
// or
export const PINNED_ROWS_EMPTY: PinnedRows = { top: [], bottom: [] };

export type PinnedRowsType = {
  top: RowEntry[];
  bottom: RowEntry[];
};

export const PinnedRows = {
  EMPTY: { top: [], bottom: [] } as PinnedRowsType
}

So there is no way to export values and types on the same identifier without modules?

not that I'm aware of.

Is it just the namespace keyword that's buggy, or using the same identifier? This works for typescript, because types and values live in separate namespaces:

export type PinnedRows = {
  top: RowEntry[];
  bottom: RowEntry[];
};
export const PinnedRows = {
  EMPTY: { top: [], bottom: [] } as PinnedRows,
};