Static binary files are mangled

[Pauan]

I am using mount to serve some static files:

module.exports = {
    mount: {
        "static": {
            url: "/",
            static: true,
            resolve: false,
        }
    },
};

Inside of the static folder I have a binary file called kloppenheim_06_1k.env.

When I run snowpack dev and try to access http://localhost:8080/kloppenheim_06_1k.env the data is completely mangled.

Here is a ZIP file which contains the original binary file (kloppenheim_06_1k.env) and the mangled file (kloppenheim_06_1k (broken).env)

Note that this file works perfectly with other HTTP servers, including with rollup-plugin-serve.

[melissamcewen]

Hi Pauan, is there a way for me to test whether or not the file is mangled? It's hard to tell if my local environment has mangled it or not from a glance.

[Pauan]

@melissamcewen The file size of the mangled file is larger than the original file (even though they should be exactly the same). You can also open it in a text editor and see the differences.

The .env files are used by BabylonJS for environment lighting, and the mangled file gives an error when trying to load it in BabylonJS.

[one-labs-de]

Hello, is there already a solution to this problem? I ran into the same problem with BabylonJS and an env map