Update the frontend dependencies and configuration #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the frontend dependencies and configuration to use newer versions of Node.js, Next.js, and several related packages. It also adds security-focused overrides and makes minor workflow and script adjustments. The most significant changes are grouped below.
Dependency and Tooling Upgrades:
Updated major dependencies in
package.jsonandpnpm-lock.yaml, includingnext(15.5.4 → 16.0.10),react/react-dom(19.1.0 → 19.2.3),lucide-react,maplibre-gl,recharts, andredis, as well as dev dependencies like@biomejs/biomeand@types/node. This ensures compatibility with the latest features and bug fixes. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Increased the required Node.js version for the frontend by removing the
.node-versionfile specifying 22.16.0, and updating engine requirements in dependencies. [1] [2]Security and Maintenance:
pnpmoverride for thetarpackage (to version >=7.5.2) in bothpackage.jsonandpnpm-lock.yamlto address known vulnerabilities. [1] [2] [3]Build and Script Changes:
--turbopackflag from thedevandbuildscripts inpackage.json, reverting to the standard Next.js build process.Workflow and Metadata:
.github/workflows/deploy.ymlfrom "Deploy to VPS" to "Deploy" for clarity.These updates collectively modernize the project's dependencies, improve security, and streamline development and deployment processes.