Feature request: Include TypeScript .d.ts file with the npm package

Expected Behavior

As the project is written in TypeScript, I would expect it to also allow using the tool with it’s typings and to benefit from the defined types when writing migration scripts.

Actual Behavior

The npm package includes only the transpiled code so no types are available.

Possible Solution

Create a separate .d.ts file for the API calls used in the documentation and include it in the npm package.

[ristomatti]

@joshmedeski I’m not at the computer right now but try adding – before the -s parameter. We’re using this with the “use as a library” method. I have created a .ts file which imports the cli module similarly as in the JavaScript example. The parameter handling is done by the script though.

I’m pretty sure though I did the initial test with the command from the new documentation though…

@Khaledgarbaya I noticed the changes being applied through commits today. I’ll try to find time tomorrow to do a PR on the improvements on the typings file.

[ristomatti]

@Khaledgarbaya it seems all but one of the changes I’ve done have been added there meanwhile. I don’t bother making a PR from that.

The only change missing was adding | number[] to IValidation.in. I added it as otherwise migration file generated with contentful space generate would not have been valid.

export interface IValidation {
  in?: string[] | number[],