Compiling js for core and core extensions

Johann

May I suggest someone, a caritative soul, a good samaritan, etc. to compile the JS files and commit them on master for core and bundled extensions? (I guess this person needs to be someone at the dev team)

Is this not something that can be a candidate to be automated on CI?

clarkwinkelmann

Solutions to that issue are being discussed. I also heard it's planned to switch to webpack soon so commiting more dist files to master doesn't make sense.

Why would you need them compiled ? master should ony be used by developers, and I expect developers won't have any issue running the complication script.

Johann

clarkwinkelmann While it is not essential, it would certainly be an improvement if we have the files to be recompiled, hence I made a suggestion here (on a discussion forum) and I did not open an issue on GitHub.

Personally, I put together a bash script that takes care of setting everyting (including compiling) for me but I still see the utility that the suggestion above has for non-developers and developers, specially if the process is automated and uses the same controlled environment.

I disagree with your "master should only be used by developers" as they are not the only ones with an use case for the master branch:

As a contributor I use it to plan/test my code contributions or replicate issues before I send a PR.
As a extension dev I use it to test the compatibility of my extensions with the upcoming version and make required changes in order for it to work from day one.
As a translator I use it to test upcoming changes on my translations.
As an admin I need to test what is coming so that I can see which extensions don’t work, what changes are needed, etc. so that I can plan better the rollout for a new version.

...And certainly a developer could benefit from not having to compile files after pulling the updated source.