Fix: Make jstack compatible with Next.js 15 (#11) #14
+4,529
−22
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
|
okay thanks for that! |
|
@code-env you're welcome |
1 similar comment
|
@code-env you're welcome |
|
@joschan21 Are you going to merge this or not? |
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.
This PR makes jstack compatible with Next.js 15 by utilizing Next.js codemod commands to handle compatibility changes efficiently. The adjustments ensure that jstack integrates smoothly within a Next.js 15 environment.
Compatibility Update: Used Next.js codemods to upgrade and refactor code where necessary for Next.js 15 support.
Codemod Commands Used:
bash
Copy code
npx @next/codemod@canary upgrade latest
Testing: Verified the compatibility with Next.js 15 through local testing, confirming that all functionalities work as expected without errors.
Related Issue:
Closes #11