James

Results 15 comments of James

Yes, precisely that. `X.Y` specifically doesn't parse. `X` still parses fine. And I got that error from the latest version of StyLua, which uses Full Moon v0.18.1

I made a [PR on their repo](https://github.com/TurtleP/batteries-definitions/pull/1) when this topic was still active that fixed the issues the OP was having. It looked like the library just wasn't configured correctly....

It looks like I'm still able to compile v3.1.0, tested with MinGW from nuwen 18.0 and 19.0. This is the output I get: ``` > luarocks --version luarocks 3.9.2 LuaRocks...

Now that I updated my LuaRocks, I'm getting the same error :) ``` > luarocks --version luarocks 3.11.0 LuaRocks main command-line interface > luarocks install luasocket Installing https://luarocks.org/luasocket-3.1.0-1.src.rock luasocket 3.1.0-1...

I tried adding the same fix for `mime.core` as I did for `socket.core` in #383, and it worked? ```diff diff --git a/rockspecs/luasocket-3.1.0-1.rockspec b/rockspecs/luasocket-3.1.0-1.rockspec index 2d724ac..a386404 100644 --- a/rockspecs/luasocket-3.1.0-1.rockspec +++ b/rockspecs/luasocket-3.1.0-1.rockspec...

Would it be better to abstract away the iteration part and use a signal/callback-based interface? ```lua -- server.luau local socket = net.socket("ws://localhost:8080") socket.received:connect(function(message) socket.send("Echo: " .. message) end) socket.listen() ```...

The way TypeScript solves @MagmaBurnsV's problem is using `keyof`, a type space indexing operator, and constrained generics, shown here. Implementors of this interface would have type-safe access and mutation of...

I wrote a package-ish that watches the dependency tree for changes and runs `Bun.build` with a build config every change. https://github.com/goldenstein64/bun-build-watch Bugs exist! And they are documented as a comment...

I think instead of adding a `watch: true` flag, there could be a separate utility that watches for changes in dependencies and either runs a `for await` loop or emits...

The link sort of got fixed, it now redirects to a prefilled crash report. In the base site https://bun.report, it now gives a 400 error. ![image](https://github.com/user-attachments/assets/f33240ba-b201-4c9e-94b1-56e36ba78df4)