Manifest is missing .vsix file in "files" field

[Philreact]

Summary
I published a npm package with a .vsix file but for some reason the private extension manager is unable to locate it.

Proof

here is my package.json

here is when I npm install the package - just to show that I have a .vsix file in it.

Does anyone know how to fix this?

[joelspadin-garmin]

That error message indicates that findVsixFile() in Package.ts didn't find the .vsix file. This is the code that should be handling that.

vscode-private-extension-manager/extension/src/Package.ts

Lines 343 to 347 in 541b3b4

	for (const file of manifest.files) {
	if (typeof file === 'string' && file.endsWith('.vsix')) {
	return success(file);
	}
	}

I don't see any reason why that would fail from the portion of the package.json that you've shown. Does your package.json contain an "osSpecificVsix" field which contains neither an entry for your OS nor a "default" value?

[Philreact]

Thanks Joel for responding to my issue.

I didn't have an "osSpecificVsix" field initially but I tried adding it and I'm still receiving the 'Manifest is missing .vsix file in "files" error.

[pbance-spendesk]

The files field is indeed in the package.json. But it's missing somehow from the repository manifest that is fetched by the npm-registry-fetch package. Is it possible to configure a private registry in order to have this information in the manifest file somehow?