assets are annoying #92

New Issue

hf · 2023-12-11T09:53:22Z

hf commented

2023-12-11 09:53:22 +00:00

Currently javascript and css assets are named with a hash and listed in a json file that is loaded by the server.
The server shouldn't need that json file and should just look into the directory and check what is there.
Instead of a hash, a timestamp should be in the filename for easier sorting, making it possible for webpack to know how the file will be named before it is built.
Detecting whether or not a newly built asset is different from the previous one is the job of deployment scripts.

Currently javascript and css assets are named with a hash and listed in a json file that is loaded by the server. The server shouldn't need that json file and should just look into the directory and check what is there. Instead of a hash, a timestamp should be in the filename for easier sorting, making it possible for webpack to know how the file will be named before it is built. Detecting whether or not a newly built asset is different from the previous one is the job of deployment scripts.

hf referenced this issue from a commit

2023-12-11 15:49:51 +00:00

deprecate assets.json by reading the assets directory ourselves,

hf closed this issue

2023-12-11 15:49:51 +00:00

Sign in to join this conversation.