fix: remove unused dependency npm-watch

[dtarnawsky]

npm-watch is not used by the project (and would be a dev dependency if it were), so this PR removes it to address vulunerabilties down the line to @capacitor/assets (ionic-team/capacitor-assets#590)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
trapeze	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 26, 2024 7:52pm

[kensodemann]

Agree that npm-watch is unused, just wondering if we should also npm i as part of this PR to also clean up the package-lock.json at the root of this mono-repo.

[dtarnawsky]

Hey @kensodemann , I've updated the package-lock.json after a rebase with the hope that the open source gods will merge this PR to resolve downstream security vulnerabilities.

[kensodemann]

Hey @kensodemann , I've updated the package-lock.json after a rebase with the hope that the open source gods will merge this PR to resolve downstream security vulnerabilities.

So are you saying that the package-lock.json file is part of an existing change on main then that I cannot see here?

[dtarnawsky]

Hey @kensodemann , I've updated the package-lock.json after a rebase with the hope that the open source gods will merge this PR to resolve downstream security vulnerabilities.

So are you saying that the package-lock.json file is part of an existing change on main then that I cannot see here?

Weird, the commit showed up a lot longer than the comment. The update to package-lock.json is showing now

[markemer]

Cool, we can publish to trapezedev now - so whenever you're ready we can merge and publish. Do these tests always fail on CI?