UNSOLVED Magic Mirror Update process

[BKeyport]

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!

[sdetweil]

@BKeyport package.Json belongs to the project. There are new updates, which npm install needs to know about

[BKeyport]

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.

[mumblebaj]

@BKeyport Does the git reset --hard not work for you?

[BKeyport]

I did not know about this command, what does it actually do? (I know, it does a hard reset, but what does that entail?)

[sdetweil]

@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’

[mumblebaj]

@BKeyport I simple terms, it gets rid of local changes.

[BKeyport]

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?

[mumblebaj]

@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.

[bhepler]

@BKeyport - It should leave those alone. config.js and custom.css are not part of the github project so they won’t be overwritten.