chore: fix security vulnerabilities by updating nextjs and prisma #527
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 PR addresses several issues encountered during the build, development and usage of the frontend ui.
The primary goals were to resolve npm audit issues and prisma-related errors to clean up build warnings.
prismaand@prisma/clientdependencies have been upgrade from6.3.1to6.4.1.devIndicatorsconfiguration has been removed fromnext.config.tsto eliminate build warnings.nextdependency has been updated from15.1.7to15.5.6.