Updates and Fixes for Compatibility with Node.js > 16, Next.js 13, and Dependency Enhancements #192
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
The `next.js` dependency has been updated from version 11.1.2 to 12.3.4, and the `nextjs-progressbar` dependency has been updated from version 0.0.11 to 0.0.16. This update ensures that we are using the latest stable versions of these packages.
- Updated next.config.js to use correct next-pwa syntax - Ensured compatibility between next-pwa and Next.js versions
This commit updates the TypeScript dependency from version 4.5.2 to 4.9.5. It also updates other dependencies such as `@types/react`, `@types/react-dom`, and `@types/webrtc` to their latest versions. This update ensures that we are using the latest stable versions of these packages and improves compatibility with other libraries and frameworks. ```
- Move clsx to dependencies and upgrade to v2.1.1 * Now used in runtime code for dynamic className management - Add @types/eslint and @types/node devDependencies for improved TypeScript support
- Removed `as="a"` from Button component inside Link to avoid hydration mismatch - Ensured proper rendering during server-side and client-side rendering by leveraging Next.js 13's behavior where <Link> always renders <a> This change addresses the issue where the Button component was rendered as a button element on the server side and as an anchor element on the client side, causing a hydration mismatch.
- Updated the NetworkInformation interface to include additional properties: downlinksMax and saveData - Updated the Navigator type to include a connection property of type NetworkInformation - These changes ensure that the NetworkInformation interface and Navigator type accurately reflect the properties and structure of the network information data
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@atapas Hey can you review the PR |
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.
Description
This pull request includes a series of updates and fixes to enhance the functionality and compatibility of the project. The changes span various areas including refactoring, dependency updates, and bug fixes. The primary motivation for these changes is to ensure compatibility with Node versions greater than 16, addressing issues related to the deprecation and removal of some legacy cryptographic algorithms and their associated APIs.
Fixes # issue #191
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
NetworkInformationinterface andNavigatortype changes to ensure proper functionality.Cardcomponent is resolved.Headercomponent using Next.jsLink.next-pwawith Next.js.Checklist: