fix(webpack-plugin-kintone-plugin): use cli-kintone for pack plugin

[nameless-mc]

Why

With the CLI integration, @kintone/plugin-packer will reach EOL.
Since @kintone/webpack-plugin-kintone-plugin internally uses plugin-packer, it needs to be replaced with @kintone/cli.

What

• Replace @kintone/plugin-packer with @kintone/cli
• Add cli-runner.ts to execute cli-kintone's plugin pack command as a child process
• Update generatePlugin function to use cli-kintone
• Add documentation in README to use the keygen command for private key generation
• Disable file parallelism in tests to avoid file conflicts in shared fixtures

Note

An alternative approach would be to modularize cli-kintone's plugin-related functionality, but that would require significant effort. As an interim solution, this implementation uses child process invocation.

How to test

• Run pnpm --filter @kintone/webpack-plugin-kintone-plugin test and verify all tests pass
• Verify plugin build works correctly in a sample project

Checklist

• Read CONTRIBUTING.md
• Updated documentation if it is required.
• Added tests if it is required.
• Passed pnpm lint and pnpm test on the root directory.

[Copilot]

Pull request overview

This PR migrates @kintone/webpack-plugin-kintone-plugin from the deprecated @kintone/plugin-packer to @kintone/cli by executing cli-kintone's plugin commands as child processes.

Changes:

• Replaced @kintone/plugin-packer dependency with @kintone/cli
• Introduced cli-runner.ts to execute cli-kintone commands via child processes
• Updated plugin generation logic to use temporary files and asynchronous operations

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
package.json	Updated dependency from @kintone/plugin-packer to @kintone/cli
cli-runner.ts	New module providing wrappers for cli-kintone plugin commands
plugin.ts	Refactored generatePlugin to use cli-kintone via child process with temp file handling
index.ts	Updated to pass private key path instead of reading file content
vitest.config.ts	Disabled file parallelism to prevent test fixture conflicts
README.md	Added documentation for private key generation using cli-kintone

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Using synchronous file operations (fs.existsSync and fs.unlinkSync) in a finally block after async operations can cause issues if multiple plugin generations run concurrently. Use fs.promises.unlink with error handling instead to avoid blocking and potential race conditions.

Suggested change

	if (fs.existsSync(tempOutputPath)) {
	fs.unlinkSync(tempOutputPath);
	try {
	await fs.promises.unlink(tempOutputPath);
	} catch (error) {
	if ((error as NodeJS.ErrnoException).code !== "ENOENT") {
	throw error;
	}

[Copilot]

Overriding NODE_ENV to 'production' for all pack operations may have unintended side effects if the host application or other tooling relies on the original NODE_ENV value. Consider documenting this behavior or using a more targeted environment variable specific to cli-kintone if available.

Suggested change

	const env = { ...process.env, NODE_ENV: "production" };
	const env = {
	...process.env,
	...(process.env.NODE_ENV === "test" ? { NODE_ENV: "production" } : {}),
	};

[Copilot]

The catch block silently discards the original parsing error. Preserve the original error for better debugging by capturing it in the catch clause (e.g., catch (error)) and including it in the thrown error message.

Suggested change

	} catch {
	throw new Error(`Failed to parse plugin info JSON: ${stdout}`);
	} catch (error) {
	const originalError = error instanceof Error ? `${error.name}: ${error.message}` : String(error);
	throw new Error(
	`Failed to parse plugin info JSON: ${stdout}\nOriginal error: ${originalError}`,
	);

[shabaraba]

@nameless-mc
現状idしか使用してなさそうですが、今後nameなど他のプロパティを使うケースって出てきそうですかね？
もしなければidだけ返すメソッドでいいかなと思いました。