Type resulting object properties correctly when using change-case/keys

[dnjstrom]

When using change-case/keys I would love for the resulting object to be typed correctly without having to do an explicit cast. Currently all transformations produce unknown.

import { camelCase } from "change-case/keys"
import type { CamelCasedProperties } from 'type-fest';

const snake_cased = { foo_bar: 1 }

// Preferably the cast could be left off on the line below
const camelCased = camelCase(snake_cased) as CamelCasedProperties<typeof snake_cased>

console.log(camelCased.fooBar) // => 1

[hxtruong6]

I faced to the same issue when try to use the examples

[blakeembrey]

@hxtruong6 that is unrelated to the original report so I’ll be hiding the comment. Try searching closed issues instead, it’s because your typescript configuration is incorrect for ESM support.

[blakeembrey]

I think I closed a past issue on the complexity on typing these, but I think it could be good to have available. I would accept a PR if anyone wants to attempt this.

Previous issue: https://github.com/blakeembrey/change-case/issues/294.

[hxtruong6]

@hxtruong6 that is unrelated to the original report so I’ll be hiding the comment. Try searching closed issues instead, it’s because your typescript configuration is incorrect for ESM support.

  "module": "NodeNext",

Yes. You are right when I change the tsconfig.json with other module. Thank you.