For libraries, intended to be deployed on npm, there is the argument that it is a good idea to remove the package-lock.json.
As in this particular case the package-lock is already out-of-sync. Indicating that some tasks may have slipped the attion. For github actions it is also possible to add scheduled events. With this you can run tests regularly and get notified if the update of a dependency broke the library which will only be effective without a package-lock.json.
For libraries, intended to be deployed on npm, there is the argument that it is a good idea to remove the
package-lock.json.As in this particular case the
package-lockis already out-of-sync. Indicating that some tasks may have slipped the attion. For github actions it is also possible to add scheduled events. With this you can run tests regularly and get notified if the update of a dependency broke the library which will only be effective without apackage-lock.json.