Improve degraded performance by Next.js migration #101
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
xicri
force-pushed
the
perf/nextify
branch
3 times, most recently
from
78d8bfb
to
39f1bef
Compare
You cannot redirect in `getStaticProps()`.
On Next.js, 308 is default HTTP status code for permanent redirection
xicri
added a commit
that referenced
this pull request
May 21, 2023
xicri
added a commit
that referenced
this pull request
May 21, 2023
xicri
added a commit
that referenced
this pull request
May 30, 2023
This commit reverts migration to Next.js from Nuxt 2. Next.js consts too much for a personal development. I will migrate to Nuxt 3 instead. This commit reverts PRs #93, #101, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113 and #114. Apply following PR manually after migration to Nuxt 3: Check if I need to manually apply following PRs:
xicri
added a commit
that referenced
this pull request
May 30, 2023
This commit reverts migration to Next.js from Nuxt 2. Next.js consts too much for personal projects. I will migrate to Nuxt 3 instead. This commit reverts PRs #93, #101, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113 and #114. Apply following PR manually after migration to Nuxt 3: Check if I need to manually apply following PRs:
xicri
added a commit
that referenced
this pull request
May 30, 2023
This commit reverts migration to Next.js from Nuxt 2. Next.js consts too much for personal projects. I will migrate to Nuxt 3 instead. This commit reverts PRs #93, #101, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113 and #114. The following PRs should be manually applied after migration to Nuxt 3: #106 #107 #108 #110 #111 #112 #114 Check if the following PRs should be applied manually after the migration to Nuxt 3: #101 #105
xicri
added a commit
that referenced
this pull request
May 30, 2023
This commit reverts migration to Next.js from Nuxt 2. Next.js costs too much for personal projects. I will migrate to Nuxt 3 instead. This commit reverts PRs #93, #101, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113 and #114. The following PRs should be manually applied after migration to Nuxt 3: #106 #107 #108 #110 #111 #112 #114 Check if the following PRs should be applied manually after the migration to Nuxt 3: #101 #105
Merged
9 tasks
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.
Fix degraded performance by: