Read the statement by Michael Teeuw here.
Attempting To Update
-
@lavolp3 Because they are automatically generated files, you don’t include them in a repository.
package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json. It describes the exact tree that was generated, such that subsequent installs are able to generate identical trees, regardless of intermediate dependency updates.
-
This post is deleted! -
@ultimatum22 tried what you said but got the following…
Your help is appreciated; am I using the correct command to update my MagicMirror
-
@kumartrd You just tried to remove the same file twice, that’s all. You’re almost there. Try:
cd ~/MagicMirror rm package-lock.json
And while I have you here… please use the Markdown features of the board in the future when posting code and error messages. Thanks.
-
-
@justjim1220 He already got that one.
-
The
git pull
command fails if files are locally changed, because the pull would override them.
Withgit diff
you can see what has changed.If you are not interested to save these local changes you can run
git reset --hard
. This will revert all changes and after this thegit pull
should work. -
@Ultimatum22 hey there went to do the most current update and ran into the same issue with the vendor/package-lock.json package so I ran the removal script as stated below and it worked and now my pi is updated… I remember you brought up that I should have that package in a gitignore file how do I move it over?