feat: remove build-env #4660
Reference in New Issue
Block a user
No description provided.
Delete Branch "(deleted):feat/remove-build-env"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The only thing specifying a build env introduces at the moment is compiling the less instead of inserting a script for compiling it in browser.
The only real benefit of this is no dependency on lessc for compiling locally.
But it also introduces a divergence between dev env and production env, which is not ideal. It is a nontrivial divergence, as we never really update the less script, while the lessc version on the build server is updated whenever that server is updated. So we can have very divergent versions of lessc in use.
Removing
--build-envit simplifies the logic and ensures a more consistent website build.I have checked the output of building using current master branch with
--build-env fsfe.organd on this branch, and there is none. Differences were checked for usingdiff -r.This is a nonbreaking pr, as the argument is kept but simply no longer has any effect and will give a deprecation warning.
feat: remove build-envto WIP: feat: remove build-envb22720c680toe906c7ce95WIP: feat: remove build-envto feat: remove build-enve906c7ce95to4879f24ab24879f24ab2tofbf268abf6fbf268abf6to170770e040Latest tweak stops copying less to the output, as its now unnecessary. Just a slight efficiency improvement.
Will conglomerate these changes in a full python rewrite
Pull request closed