Typescript issue after types change in 3.1.0

[jekh]

The types update in 3.1.0 appears to have caused an issue when importing and using Anvil in a typescript project, at least when using ESM.

In 3.1.0 (but not 3.0.1), typescript appears to think Anvil is a namespace, and doesn't recognize it as a class.

This expression is not constructable.
  Type 'typeof import("file:///node_modules/@anvilco/anvil/types/src/index")' has no construct signatures.

The issue appears to occur because of this change in index.d.ts from export = Anvil to export default Anvil. Manually changing that single line back appears to fix the type error.

I'm not totally sure why that change would cause this issue, or what the implications of it are. Only that it does seem to be the culprit!

[newhouse]

Hi @jekh we'll have a look. Is this blocking you right now, or is it just an annoyance?

[newhouse]

Hi @jekh we'll have a look. Is this blocking you right now, or is it just an annoyance?

[jekh]

Hi @jekh we'll have a look. Is this blocking you right now, or is it just an annoyance?

It does block us from upgrading, yes, since it won't compile.

[newhouse]

@jekh

Can you try changing your import to something like this:

import Anvil from '@anvilco/anvil/dist/index.js'

const client = new Anvil({...})
...

I was able to get TSC to understand the type that way and successfully compile. We will fix the root problem at some point, but I think for now this is a good workaround.

Let me know if this works!

[newhouse]

@jekh did that work for you and allow you to upgrade?