Problem with source-map-loader when using webpack: "The keyword 'interface' is reserved" about io-ts HOT 8 CLOSED

Actually using
t._interface
is ALREADY available, so that's all I needed.

from io-ts.

I am reopening this issue because, the same problem happens with
t.null

from io-ts.

@gcanti the problem is pretty general in this setting.
Maybe we can double all the exported definitions whose names match reserved keywords?

from io-ts.

@sledorze Could you please put up a repo reproducing the error?

Based on your description though, it doesn't seem an issue with io-ts, it rather seems a bug in the transformer

from io-ts.

@sledorze anyway I'm ok with exporting some alias, I propose

• type as an alias of interface
• nullType as an alias of null

does undefined raise an error too? (EDIT it shouldn't)

from io-ts.

@gcanti undefined is 'correctly webpacked' to something like: undefined as undefined$1
I think it could help a lot of people.
nullType is ok
type may also be a reserved keyword, the existing _interface is fine to me but if we aim at homogeneity, why not interfaceType ?

from io-ts.

type is not a reserved keyword. Also seems appropriate

type Person = {
  name: string
}

const Person = t.type({
  name: t.string
})

from io-ts.

It is a typescript keyword, not a js one, you're right
Hoping it will not pose an issue with tooling then :)

from io-ts.