Jens Reimann
Jens Reimann
As trunk only calls `minify-js`, I think you would need to raise an issue with them: https://github.com/wilsonzlin/minify-js With trunk, you can disable minification in release builds, using `data-no-minify` on assets...
I am leaning towards closing this one, as it not directly a trunk issue, and the minification defaults will change in 0.20.0.
I think trunk 0.19.0 actually brought support for this: https://trunkrs.dev/advanced/#base-urls-public-urls-paths-reverse-proxies
I think we way it needs to be wired up is using an nginx reverse proxy. There's an example for that: https://github.com/trunk-rs/trunk/tree/main/examples/behind-reverse-proxy The idea is to service an application from...
> It works, but it's not ideal I agree that it could be more comfortable. If you want to come up with a design for this, I think that would...
> Along with https://github.com/trunk-rs/trunk/issues/750, I would like to make the case for turning minification off by default. Stability matters most Yes and no. I agree with that in general. On...
I am closing this one, as it's not directly a trunk issue. And minification defaults will change in 0.20.0.
I am not sure what the exact problem is. I do recall issues where the JS file was actually a module JS file. That can make a difference. For that...
I am not sure if there's something that trunk could do better? If so, please let me know.
I guess so. Having that would be nice.