Type constructor `CustomType` breaks js codegen

[lucasavila00]

[lpil]

Oops haha! That's quite a funny edge case. We'll have to fix that one.

[lpil]

One solution might be to import constructors under a different name if there is a clash. Or perhaps we always import under a different name to make the code simpler.

What might we rename them to?

[lucasavila00]

Perhaps they should be imported with the Gleam prefix, for clarity. Although I think it would still require checking for a GleamCustomType export, and changing the alias if that creates a collision.

[lpil]

Perhaps we copy modules and use a $ prefix. Then it will never collide

import { CustomType as $CustomType } from "./gleam.js";

export Thingy extends $CustomType {
  ...
}

[lucasavila00]

Yeah, that's better.