Migrate Next to version 15 and eslint to version 9 #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…or cookie handling
…and components for improved functionality
…ar components with new variants
…s to pdf download
EasySouls
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hold on a little bit, with merging this pr, I also upgraded Prisma to v6, but they changed that the Bytes type now returns Uint8Array instead of Buffer, and I'm having a little trouble with the images. Also I want to use next/image instead of img tags, so the images are optimized |
…date controller methods to specify return types
- I don't know why it was there - Please don't check git blame, it was not me, I promise
- one container for running only the db - and another for running the entire backend locally
- If a user or an application period had no pfp/background set, it would call the backend in an endless loop - Now it fetches the images using useFetch with the cacheBuster, so the images still automatically reload upon uploading - Also set a padding on the badges to make the look nicer
- Footer was not at the end of page - Fix eslint not used variable errors - Center the footer
|
@mozsarmate @FearsomeRover I think I am brave enough to say that the migration is fully done. But rather prove me wrong than deploy it with errors. I also had to change a few other stuff not related to the migration, but they only improved the UX (I hope). |
mozsarmate
approved these changes
Dec 12, 2024
mozsarmate
added a commit
that referenced
this pull request
Dec 12, 2024
* summarized posts, second banner card, 24 recap * design updates * updated footer * 2024 recap update * Migrate Next to version 15 and eslint to version 9 (#138) * Add Yarn configuration, update Next.js and React versions, and refactor cookie handling * Update package dependencies and ESLint configuration, refactor hooks and components for improved functionality * Update every non-breaking package * Modify imported shadcn-ui compoponents * Update react-day-picker to version 9.3.0 and enhance badge and calendar components with new variants * Update ESLint configuration, add launch options for next and add types to pdf download * Separate utility functions, so the pdf generation can run on the client * Remove eslint config from root project and fix errors in frontend * Add new eslint config file to backend as well * Enable corepack and yarn v4 in github analysis action * Fix import and conditional useCallback * Update React from rc to stable version * Update react icons * Fix react icon import * Generate prisma client in build github actions * Update JSX import * Update Next minor version * Update Buffer to Uint8Array in images, and prisma to v6 * Refactor image handling to return Buffer instead of Uint8Array and update controller methods to specify return types * Remove prisma dependency from frontend - I don't know why it was there - Please don't check git blame, it was not me, I promise * Add new docker compose files - one container for running only the db - and another for running the entire backend locally * Fix image loading - If a user or an application period had no pfp/background set, it would call the backend in an endless loop - Now it fetches the images using useFetch with the cacheBuster, so the images still automatically reload upon uploading - Also set a padding on the badges to make the look nicer * Fix minor errors - Footer was not at the end of page - Fix eslint not used variable errors - Center the footer * Fix eslint errors * return prof-pic-status on /user/me --------- Co-authored-by: EasySouls <93796810+EasySouls@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Next
Debugging Configurations:
.vscode/launch.json.Dependency Updates:
ESLint:
Yarn:
React: