fix(deno): update types for deno ^1.4.0

[luke-john]

In version 1.4 Deno adopted;

• the tsconfig setting importsNotUsedAsValues - feat(unstable): enable importsNotUsedAsValues denoland/deno#7413
• the tsconfig setting isolatedModules when using the deno --unstable flag - Use isolatedModules denoland/deno#7326 (intended to be enabled by default in 1.5)

These require the use of;

• type only imports for values which are only used as types (importsNotUsedAsValues)
• type only exports for types which are re-exported (isolatedModules)

I've added more details at #1771.

related prs:

• yargs-parser fix(deno): update types for deno ^1.4.0 yargs-parser#329
• y18n fix(deno): update types for deno ^1.4.0 y18n#100

[luke-john]

While preparing this pr and the related ones in yargs-parse and y18n, vscode showed most files as full of errors due to the use of file extensions in imports which don't match the actual source files extension

ie

// https://github.com/yargs/yargs/blob/master/lib/typings/yargs-parser-types.ts#L3
import type { Dictionary, ValueOf } from './common-types.js'

In this example common-types is a typescript file with the extension .ts common-types.ts

While there's some build tooling and to support the builds to the build folder, I was still seeing issues in the files under /build.

Are these intentional (possibly for the cjs builds)?

[bcoe]

@luke-john I will need to dig into these CI/CD issues, I just fixed a bug related to how we parse commands, not sure how I failed to update this failing test.

[luke-john]

No problems, I've just updated this to be against master instead of Deno.

[bcoe]

@luke-john hey Luke, just wanted to let you know that the latest version of yargs should have this problem fixed for you.

Let me know if you continue to bump into any issues?