New package: Oven-sh.Bun version 1.1.0

[mdanish-kh]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[sitiom]

• Related: New package: Oven-sh.Bun.Baseline version 1.1.0 #147226

[sitiom]

As suggested by @paperdave, a CPU check like this would be nice, but I guess it's not possible with Winget yet:

if (-not (Add-Type -MemberDefinition '[DllImport("kernel32.dll")] public static extern bool IsProcessorFeaturePresent(int ProcessorFeature);'-Name 'Kernel32'-Namespace 'Win32'-PassThru)::IsProcessorFeaturePresent(40)) {
    Write-Host -Foreground Red "This CPU does not support the AVX2 instruction set. Please install 'Oven-sh.Bun.Baseline' instead."
}

[mdanish-kh]

As suggested by @paperdave, a CPU check like this would be nice, but I guess it's not possible with Winget yet:

if (-not (Add-Type -MemberDefinition '[DllImport("kernel32.dll")] public static extern bool IsProcessorFeaturePresent(int ProcessorFeature);'-Name 'Kernel32'-Namespace 'Win32'-PassThru)::IsProcessorFeaturePresent(40)) {
    Write-Host -Foreground Red "This CPU does not support the AVX2 instruction set. Please install 'Oven-sh.Bun.Baseline' instead."
}

Yes, I don't think that's possible with WinGet. We can have a note printed out after installation though that says something like:

If you face issues running the package, it might be because your CPU does not support AVX2 instruction set. In that case, try installing Over-sh.Bun.Baseline instead.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[sitiom]

I forgot about this too, a bunx alias for bun x (Bun automatically detects the naming):

Suggested change

	PortableCommandAlias: bun
	PortableCommandAlias: bun
	- RelativeFilePath: .\bun-windows-x64\bun.exe
	PortableCommandAlias: bunx

[sitiom]

• Update version: Oven-sh.Bun version 1.1.0 #147295