chore: allow node globals in script lint config #16
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@vitejs/plugin-react-swc": "^3.10.2", | ||
| "eslint": "^9.38.0", | ||
| "favicons": "^7.2.0", | ||
| "globals": "^15.14.0", |
There was a problem hiding this comment.
Update lockfile after adding globals dependency
The commit adds globals to the web UI devDependencies but does not regenerate package-lock.json. Because the lockfile is checked in, npm ci (or any install that relies on the lockfile) will fail with an out‑of‑sync error and the lint configuration will not resolve the new package. Run npm install and commit the updated lockfile so the dependency can be installed reliably.
Useful? React with 👍 / 👎.
No description provided.