client/modules/scalar.ts causes runtime errors when using custom scalars

[P4sca1]

Generated code:

import * as CustomScalars from '../../../scalars.js'
export * from '../../../scalars.js'
export { // 
	MyScalar,
// ...
} from '../../../scalars.js'

// ...

export const $registry = {
	map: {
		MyScalar: MyScalar, // Runtime error
// ...
	},
} as $Registry

In the first export statement, all custom scalars are exported. The next statement explicitly exports all scalars, which is redundant. Later in the runtime scalar registry, the scalar is undefined. This can be fixed in 2 ways:

1. Change the explicit export to an import statement. The export is unneeded because all scalars are already exported. The CustomScalars import can be changed to a type-only import.
2. Remove the explicit export and use CustomScalars.MyScalar in the runtime registry.

[jasonkuhrt]

Thank you for reporting @P4sca1!

[P4sca1]

@jasonkuhrt The runtime errors are gone now, but I get type checking errors now:

graphql/generated/client/modules/schema-driven-data-map.ts:45:30 - error TS2339: Property 'CountryCode' does not exist on type 'typeof import("/graphql/generated/client/modules/scalar")'.

45 const CountryCode = $$Scalar.CountryCode
                                ~~~~~~~~~~~

[jasonkuhrt]

@P4sca1 ok will take a look