Has anybody experience using this package with cabal?

My problem is that the FilePaths can only be resolved if I give the absolute Path, but I would like the package to be self-contained.
Specifying data-dir in the .cabal file and accessing the file via getDataDir does not work since the files are needed at compile-time, not at runtime.

It takes long compile time when one of the front-end files becomes to be around 100K bytes.
A 100K bytes js files are likely such as one it imports babel-polyfill.

After installing dependent libraries,
stack build --flag servant-static-th:buildexample takes

• 19 seconds on current latest master (7ae9924)
• 350 seconds with 92K bytes js file

It must be a sort of bottleneck to let people to use this fantastic servant-static-th in real world applications.

Hi,

I wonder if it's possible to modify the public API of this library in a way that would allow embedding of compressed assets? The idea is to apply the most aggressive gzip compression on JS/CSS assets as part of a build pipeline, so that they are served directly as gzipped resources without having to spend CPU cycles on on-the-fly encoding.

It's a hidden file created by Mac OS in many directories. I can be safely ignored for the purpose of this library.

Is there a way to configure servant-static-th to map particular file to / path? Based on the documentation there doesn't seem to be a way to do this currently. Is there a way around this limitation?

Is there a recommended way of generating type-safe links for a directory who's API has been created by createApiAndServerDecs?

These are source-map files for minified / uglified CSS/JS files. There should probably be a config option in the user-facing API which controls whether these files should be served, or not.

Hello,
I have static files (.sass) that do not need to be served but ignored by the extensionToMimeTypeInfoEx function
Right now, it fails with "unknown extension type"
Do you have a plan for such issue already ?
Thanks for your reply.
Alexandre