Ashcon Partovi

FYI, I will be bringing this back, though it's not ready yet.

The user seems to resolve correctly: https://api.ashcon.app/mojang/v2/user/f0369554-7707-486a-b230-8518f04102f7

@robobun ```js const url = "wss://stream.data.alpaca.markets/v2/iex"; const socket = new WebSocket(url); socket.onmessage = function(event) { console.log("on message event triggered"); const data = JSON.parse(event.data); console.log("On message event: ", data[0]); if (data[0]["msg"]...

This appears to work as of Bun v0.5.0, at least on MacOS and Linux. Does this still happen when you try again? ```sh bun upgrade --canary ```

Tested again, marking as fixed. Let us know if you are still able to reproduce this issue.

The headers have been fixed, browsers will download it as an attachment, which is in-line with other install scripts. ``` < content-type: application/x-sh < cf-ray: 81b5b5bf7faa679a-SJC < cf-cache-status: DYNAMIC <...

We will not be officially supporting Android/iOS for the foreseeable future.

`bun dev` and `bun bun` were changed in Bun v1.0, it will now run the "dev" script in your package.json, and run `bun build` respectively. Because of that, this issue...

Thanks for submitting this PR, we fixed this a while ago.

We've made very significant changes and improvements to `bun create` and `bun install` between Bun v0.1 and Bun v1.0. Specifically, we fixed some of the issues around hanging a while...