fix(tsconfig): add exactOptionalPropertyTypes

[douglasduteil]

Description

Additional context

---

What is the purpose of this pull request?

• [x] Bug fix
• [ ] New Feature
• [ ] Documentation update
• [ ] Other

Before submitting the PR, please make sure you do the following

• [x] Read the Contributing Guidelines.
• [x] Follow the Style Guide.
• [x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• [x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

[mskelton]

Why?

[douglasduteil]

I experimented some issues with tailwind-variants and this compiler options. I'm wandering if the same errors hit the tailwind-variants tests.

Some like :

import { tv, type VariantProps } from "tailwind-variants";

const button = tv({
  variants: {
    intent: {
      primary: "bg-primary"
    }
  }
})

function DatButton({ intent }:  VariantProps<typeof button>) {
  return <button className={button({ intent })} />
}

Result with :

Type error: Argument of type '{ intent: "primary" | undefined;  }' is not assignable to parameter of type '({ intent?: "primary" } & ClassProp<...>) | undefined'.
  Type '{ intent: "primary" | undefined;  }' is not assignable to type '{ intent?: "primary" } & { ...; }' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
    Type '{ intent: "primary" | undefined;  }' is not assignable to type '{ intent?: "primary" }' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
      Types of property 'intent' are incompatible.
        Type '"primary" | undefined' is not assignable to type '"primary"'.
          Type 'undefined' is not assignable to type '"primary"'.

[mskelton]

@douglasduteil Thanks for the example. I updated the type decls to support exactOptionalPropertyTypes

[douglasduteil]

🎉 Thanks @mskelton