Currently, production js files are put into site/js/release.{version}/{name}.min.js and css files are put into site/css/release.{version}/name.{version}.css, and the old files are not cleared out.
Edit: These files are not in the repo, but they do stack up on machines, including the r6maps server.
This means that every version, package.json and any html file specifying a js or css file must be manually updated.
Is there a reason this is the case? IMO it would be easier to overwrite previous versions of these files, and not have to keep track of the version all over package.json and in any file referencing the js or css files.
If we were to do so, my proposed structure for the site folder is as follows:
Currently, production js files are put into
site/js/release.{version}/{name}.min.jsand css files are put intosite/css/release.{version}/name.{version}.css, and the old files are not cleared out. Edit: These files are not in the repo, but they do stack up on machines, including the r6maps server.This means that every version,
package.jsonand any html file specifying a js or css file must be manually updated.Is there a reason this is the case? IMO it would be easier to overwrite previous versions of these files, and not have to keep track of the version all over
package.jsonand in any file referencing the js or css files.If we were to do so, my proposed structure for the
sitefolder is as follows: