You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yep the original file for scripts is this one
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
}
The app launch doesn't depend on the hash, right @hugo2410 ?
@mAkeddar@mischakolbe having the git hash before building allows us to have for every single build. So, we are sure that even if we get the versioning wrong (as it is done manually) we are able to trace back to the specific version of the code. It would allow us to debug easier. I can try and investigate how we need to adapt the path to make it work cross-platform
Fair point, Hugo. Good to know! If it gets embedded into the build to make
it reproducible it's another story. At first glance it looked like it was
just for a printout when running npm start.
Are these fancier start/build/test scripts in the package.json required?
I got errors on Windows (terminal, bash & powershell) and a hacky equivalent probably doesn't work on Mac...
I don't think the commit hash is very necessary and we could just switch to this?
The text was updated successfully, but these errors were encountered: