You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you @c-bertran for your effort put into fixing this. I really appreciate it and thank you. Error 500 has been fixed, but unfortunately, a few new errors have appeared now.
In the express-autoindex@^1.3.0 version, the character encoding for static files has stopped working correctly.
Thank you also for adding the customTemplate option! There is no other npm module like yours, so I plan to use it anyway - even if it doesn't work perfectly 100%.
I've just added the best possible management of file encoding. It's quite complex and it's possible in some rare cases for the encoding to be unsuitable, but frankly there's very little risk.
As for the endpoints, I've been working on them for a while, and I'm confident I'll find a solution.
Thank you @c-bertran for your effort put into fixing this. I really appreciate it and thank you. Error 500 has been fixed, but unfortunately, a few new errors have appeared now.
express-autoindex@^1.3.0
version, the character encoding for static files has stopped working correctly./xxx/yyy/zzz/generated
do not work withexpress-autoindex
, even though they are correctly served statically.Thank you also for adding the
customTemplate
option! There is no other npm module like yours, so I plan to use it anyway - even if it doesn't work perfectly 100%.Originally posted by @sefinek24 in #1 (comment)
The text was updated successfully, but these errors were encountered: