Allowing publishConfig.directory to not expect an existing package.json

[sharky98]

Hello,

I was wondering why, using the publishConfig.directory, we must create a manual package.json as per the docs?

When not using it, pnpm seem to be able to generate the correct package.json file from the @pnpm/exportable-manifest package.

Is there a technical reason to not re-use that code to generate the package.json, even when using publishConfig.directory?

This would help in keeping in sync both versions when publishing.

pnpm/pkg-manifest/exportable-manifest/src/overridePublishConfig.ts

Lines 29 to 43 in d5c40b5

	export function overridePublishConfig (publishManifest: ProjectManifest): void {
	const { publishConfig } = publishManifest
	if (!publishConfig) return
	Object.entries(publishConfig)
	.filter(([key]) => PUBLISH_CONFIG_WHITELIST.has(key))
	.forEach(([key, value]) => {
	publishManifest[key as keyof ProjectManifest] = value as any // eslint-disable-line @typescript-eslint/no-explicit-any
	delete publishConfig[key]
	})
	if (isEmpty(publishConfig)) {
	delete publishManifest.publishConfig
	}
	}