| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Why do we need to update all of the packages? |
Sorry, something went wrong.
Just going on an update spree. Dependabot has been submitting a few PRs here and there so I figure it's best to keep packages up to date: #73 Also these alerts: https://github.com/actions/setup-python/network/alerts |
Sorry, something went wrong.
A few tricks here to help:
* text=auto .gitattributes will override anyone's local Git config, so we don't have to rely on everyone having the same core.autocrlf settings. |
Sorry, something went wrong.
|
@brcrista figured it out, * text=auto is needed along with eol=lf. I suspect git might have some different settings during checkout on our runners which is why this weirdness was happening. I followed the recommendations here: https://prettier.io/docs/en/options.html#end-of-line |
Sorry, something went wrong.
* Update NPM packages * Format using prettier * Update node version in workflow * Add .gitattributes
| Back | FazBrowse Home | New Git URL |
Sanity check to make sure everything works before going to master: https://github.com/konradpabjan/Testing2/runs/533477128?check_suite_focus=true
This should make the security warning go away that we're seeing.
I used ncu to update all the packages (haven't found a better way to update all npm packages)
https://stackoverflow.com/questions/16073603/how-do-i-update-each-dependency-in-package-json-to-the-latest-version
Also npm run format-check is green on my windows box, but it's failing here?!? looks like it's just line endings so that can be ignored, still curious as to why (I've got CRLF in vscode and core.autocrlf set to true for git)?