What is the expected default behaviour for package export jest snapshots

[BrknRules]

Did a drop in upgrade from ts-jest to @swc/jest and found my snapshots were slightly different. All of our exported types from our index.ts have changed from not being emitted at all, to being emitted as undefined. Other exports within index.ts were correctly being exported as functions, however.

// this react component exports correctly as a function
export { Component } from './Component';

// this hook also exports as a function
export { useContainer } from './hooks/useContainer'

// these types previously did not emit anything, but now are emitted as defined.
export {
  ComponentProps,
  DynamicVariant,
  StaticVariant,
  ContainerProps,
} from './types';

Here was the snapshot with ts-jest:

exports[`@pandora/react-mat-dialog index should have the expected exports 1`] = `
{
  "Component": [Function],
  "useContainer": [Function],
}
`;

and here is swc/jest:

exports[`@pandora/react-mat-dialog index should have the expected exports 1`] = `
{
  "DynamicVariant": undefined,
  "Component": [Function],
  "ContainerProps": undefined,
  "ComponentProps": undefined,
  "StaticVariant": undefined,
  "useContainer": [Function],
}
`;

According to this issue, my understanding is that swc's default behaviour is to not emit these properties at all, instead of emitting them as undefined.

I've not set any configuration for swc as well, this is a clean drop in. Was wondering if this is expected behaviour and I should update my snapshot, or if I should find some configuration option to match the old behaviour.

[kdy1]

You should add type keywords if those are types. https://swc.rs/docs/migrating-from-tsc#importsnotusedasvalues-error