Ethan Frei

We're using this plugin and play framework 2.2.1. Still same issue. @m-j have you done anything to help with this? It seems we must modify and unmodify `main.css` every time...

I wrote [a little gist](https://gist.github.com/freiguy1/1f7e9606288561a51cc9) about what I did. Maybe that will point you in the right direction.

I think I've solved this in an unconventional way. I use elmapp.config.js's `setupProxy` in a way it wasn't meant to. ```js module.exports = { setupProxy: (app, server) => { this.proxy...

That makes sense! I could attempt something, but I guess I'm not sure where to start. Would the stub wasm4 be written in c, or could I do it in...

Ooh, maybe I can use this from the zig docs: >Use the compile variable `@import("builtin").is_test` to detect a test build

Okay I'll use zig for the stub. I think it's the _linking_ part that I'm confused on. I guess I'm not sure how to link to the stub when testing...

Okay then this new test.zig file would no dependency on wasm4 (aka wouldn't `@import` it) and no dependency on main.zig (which depends on wasm4), right?

Ooh using `usingnamespace`, I think I got something that's pretty optimal (not much repeated code and unobtrusive in main.zig) https://gist.github.com/freiguy1/aec1cbd670b3be6d52b60e22ff69614b It's all in one file.

I see the same problem almost exactly a year later. I'm running Linux using macroquad 0.3. I think it might be because the text is rendered at font size 1...

Ah, fixed it by using `draw_font_ex` with params which address scaling. First, create a `TextParams`: ```rust let (font_size, font_scale, font_aspect) = camera_font_scale(1.); let text_params = TextParams { font_size, font_scale, font_scale_aspect:...