Currently the client code is generated in the development machine. This means that every time we want to push to the server, we have to run yarn run deploy:prod on the local machine. The generated file names has a hash between the filename and file extension (ie app.28f32jdi123fnbvbh.js) for cache busting.
Since the generated files are in the git repository, it makes collaboration difficult. Every time someone pushes with a newly generated files. Another developer will get merge conflicts when he/she tries to push.
The ideal is Azure needs to generate the static assets during the build process. This will make development with multiple developers much easier, eliminating merge conflicts.
Currently the client code is generated in the development machine. This means that every time we want to push to the server, we have to run
yarn run deploy:prodon the local machine. The generated file names has a hash between the filename and file extension (ieapp.28f32jdi123fnbvbh.js) for cache busting.Since the generated files are in the git repository, it makes collaboration difficult. Every time someone pushes with a newly generated files. Another developer will get merge conflicts when he/she tries to push.
The ideal is Azure needs to generate the static assets during the build process. This will make development with multiple developers much easier, eliminating merge conflicts.