UNSOLVED Magic Mirror Update process
-
Can you please take “package.json” & “package-lock.json” out of the update for future releases so that we don’t have to remove them to update?
Thanks!
-
@BKeyport package.Json belongs to the project. There are new updates, which npm install needs to know about
-
I always have to delete package.json when updating, this is why I’m asking… If there’s a smarter way to do that, please do.
-
@BKeyport Does the
git reset --hardnot work for you? -
I did not know about this command, what does it actually do? (I know, it does a hard reset, but what does that entail?)
-
@BKeyport see the number 1 answer
https://stackoverflow.com/questions/2530060/in-plain-english-what-does-git-reset-do
this result from google search ‘what does git reset hard do’
-
@BKeyport I simple terms, it gets rid of local changes.
-
Ahh, I see - it looks dangerous from what I’ve seen - would it kill my config.js and/or custom.css, or does it leave those alone?
-
@BKeyport From my experience they don’t get touched. I have never had any issues with my mirror or modules after running that command and updating the mirror.
-
@BKeyport - It should leave those alone.
config.jsandcustom.cssare not part of the github project so they won’t be overwritten.
