Good stuff @bgptr.

The npm update workflow is something that I should document though, because there is a process to follow to minimize extraneous updates. But the first thing is that you'll need to update npm because we've been on lockfileVersion 2 since npm 7 (I'm on 8 now). This is the main reason for the huge deletion count in your current diff.

The first step when making changes to npm deps is to start with the package.json and package-lock.json as on master and do an npm clean-install (npm ci) rather than npm install so that it installs the versions from the package-lock.json file into node_modules. Doing npm install first when there is no node_modules folder yet will fetch latest from the internet of whatever satisfies package.json (too much) and install those instead of what's in package-lock.json.

git restore --source master package.json package-lock.json
npm clean-install                         # populate node_modules as per package-lock.json
git add package.json package-lock.json    # checkpoint

Then to update just one package, three approaches:

• Just edit the package.json manually then do npm i to update the package-lock.json.
• Use ncu (i.e. ncu --target latest -f bootstrap -u) followed by npm i to apply. The ncu approach is usually most useful when updating multiple packages across major versions.
• npm install bootstrap@5.1.3 -D, which updates package.json and package-lock.json in one shot. I'd do this.

Note that with the local node_modules folder populated after doing npm clean-install at the beginning, doing npm install subsequently will minimally update the package-lock.json rather than trying to get the latest acceptable versions of everything from the npmjs registry.

$  npm install bootstrap@5.1.3 -D --no-fund

added 1 package, removed 2 packages, changed 1 package, and audited 686 packages in 1s

found 0 vulnerabilities

$  git diff --stat
 client/webserver/site/package-lock.json | 68 ++++++++++++++++++++++++++------------------------------------------
 client/webserver/site/package.json      |  2 +-
 2 files changed, 27 insertions(+), 43 deletions(-)

$  git add package.json package-lock.json

Finally, follow it up with an npm dedup. It may change nothing, but I always do this before committing.

You are welcome to do some other dep updates selectively, but they should be in a separate commit. npm out says there's a few patch updates, but nothing looks required right now.

Thanks for resolving the misplaced "X" buttons too! Does the fix apply to the unlock dialog as well? i.e. #1441

@chappjc

Thanks for the instructions and sorry for the improper update. (The main problem was that I'm on node 14. It's best for decrediton dev now.)

I've fixed the misplaced close icon on unlock dialog too:

@JoeGruffins thanks for the review. Fixed the mentioned misplacement issue.

Thanks for the review @buck54321, nice catches. I've fixed them.

added .form-label to form labels which are now required.

What do you mean "required"?

It's a breaking change. I read it in the migration guide:

It means margin-bottom: 0.5rem;