Added type definitions

[jamesgeorge007]

Projects using typescript codebase requires to have type definitions within .d.ts files. (Alternatively they can be submitted over to the DefinitelyTyped repository and installed via npm i @types/envinfo)

[luisherranz]

I'd love this to get merged as well :)

[tabrindle]

I think your git blame is sufficient 😆

[jamesgeorge007]

It is just a convention to credit the author as found within the DefinitelyTyped project.

[byCedric]

I'd love to have TypeScript support too! But I think we need to finetune this a bit more. @tabrindle do you want to support TypeScript from this repository or do you want to "outsource" it into definitely types? 😄

[byCedric]

I think some properties fo the config is missing right? Maybe it's nice to add these too:

• Managers
• Utilities
• Servers
• Virtualization
• SDKs
• IDEs
• Languages
• Databases
• Monorepos

[byCedric]

Btw, we can also set all properties to "possible undefined" in the interface itself ofc, to fix this one. e.g.

interface Config {
    System?: string[];
    ...
}

[byCedric]

Would be great if we have type hints about the available helpers, that way we don't have to read the docs but simply check the autocompletion whats available 😄

I think it's fairly easy to set this up, but it requires some changes. if we define an interface for the helper consts, like browserBundleIdentifiers, we can do something like:

interface Config {
    Browsers: (keyOf helpers.BrowserBundleIdentifiers)[];
}

[byCedric]

Both config and options should be this, right?

function run(config: Partial<Config>, options: Partial<Options>): any

You don't have to specify all config or option keys, you only define what you need.

[byCedric]

Also, might be nice if we define the actual output of the run function instead of any. I think this should be string with any option. AFAIK it's:

• showNotFound => no effect on return value
• console => no effect on return value
• { json: true } => json string
• { json: false } => formatted string

[byCedric]

Just like npmPackages, I think npmGlobalPackages also accepts a string.

[lzm0x219]

emmm. Is there no one to deal with this pr?