Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unnecessary cached files #129

Open
purechaose opened this issue Dec 5, 2018 · 0 comments
Open

Unnecessary cached files #129

purechaose opened this issue Dec 5, 2018 · 0 comments

Comments

@purechaose
Copy link
Contributor

purechaose commented Dec 5, 2018

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:

site
|-- about
|   `-- <about pages>
|
|-- css
|   |-- about.css
|   |-- about.css.map
|   |-- main.css
|   `-- ...
|
|-- js
|   |-- about.min.js
|   |-- about.min.js.map
|   |-- common.min.js
|   `-- ...
|
`-- lib
    `-- ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant