manual build option, npm i, and remove #each keys

[kevinkace]

I updated the GH action (./.github/workflows/static.yml) to allow manually kicking off a build, and disabled automatic builds with pushes to main.

npm ci for some reason wouldn't update the package-lock.json and kept complaining that it was out of sync even after running npm i locally to update the lock file. The action completed successfully after changing to npm i.
https://github.com/kevinkace/Local-Connectivity-Lab.github.io/actions/runs/20872694540
This should be changed back to npm ci after the build completes successfully.

Lastly, I removed specifying #each keys, and updated ./estlint.config.js to suit. Keys are only required if items are added/removed from an #each, which currently we're not doing.

[abacef]

Can you remove this? I dont want this to be run outside of a push to main

[abacef]

Can you remove this comment

[abacef]

Can you remove this comment or fix the fact that it is false?

[abacef]

I currently still see the issue of not being able to follow the about-us link.

Dockerfile

from node:22.17.0

cmd ["bash", "-lc", "cd /code && npm install && npm run build && cd build && npx http-server -p 8001"]

run the container

docker run -v ./Local-Connectivity-Lab.github.io:/code -p 8001:8001

go to localhost:8001/about-us
it does not load.

There should be a file called about-us flat in the /build directory I assume?

The issue does not have to do with the type of static file server because both the python and the npx static file server give a 404

npx http-server -p 8001
python3 -m http.server 8001

[abacef]

Also it has been really hard to figure out how to run the tests locally, I still have not yet. Can you add a github action that runs the tests so we dont have to rely on our own machine?

[abacef]

Just tried again, and I am not getting the about-us not loading issue, but me and Ted seem to have found another issue

[abacef]

Run a static file server on port 5173

npx http-server -p 5173

Then in a different terminal run the tests

npm run test

The donate test fails.

You can verify this by going to the donate page directly http://localhost:5173/donate it will try to redirect forever