fix: ol --version shows the wrong version

[Copilot]

ol --version was reporting a stale hardcoded value from src/index.ts instead of the package’s actual release version. This caused version output drift whenever package.json was updated.

• Version source correction

  • Updated CLI program metadata in src/index.ts to read version from package.json rather than a literal string.
  • Aligns runtime version output with published package metadata.

• Impact

  • ol --version now reflects the current package version consistently across releases.

import packageJson from '../package.json' with { type: 'json' }

program
	.name('ol')
	.version(packageJson.version)

[doistbot]

Thank you for this update to dynamically pull the CLI version directly from package.json, which is a great maintainability improvement that ensures the runtime version always stays perfectly in sync with published releases. However, the current JSON import approach will cause a TypeScript build failure due to rootDir constraints, so the implementation will need to be adjusted to use a runtime file read instead.

_{Share Feedback • Review Logs}

[doistbot]

[P0] Build failure due to missing resolveJsonModule and rootDir violation

Importing JSON modules directly requires resolveJsonModule: true in tsconfig.json. Even if that were enabled, importing ../package.json from src/index.ts violates the rootDir: "src" compiler option, as TypeScript expects all compiled files to reside within the source directory. This will cause tsc to fail the build.

To resolve this while remaining compatible with TypeScript and ESM module resolution, read and parse the file at runtime using readFileSync and import.meta.url instead of an import statement.

Suggested change

	import packageJson from '../package.json' with { type: 'json' }
	import { readFileSync } from 'node:fs'
	const packageJson = JSON.parse(readFileSync(new URL('../package.json', import.meta.url), 'utf-8'))