Feat adds full fledge support for the next js framework by @m3e/nextjs…#32
Closed
Aditya1234vishwakarma wants to merge 1 commit intomatraic:mainfrom
Closed
Conversation
…. Implement dynamic Next.js client-side wrappers for all components. Closes matraic#26 - Manually implemented Next.js `dynamic` imports with `"use client"` directives for all `@m3e/react` components. - Extracted and correctly typed all parent components along with their respective subcomponents (e.g., `M3eDialogAction`, `M3eListItem`, etc.) to ensure strict type compliance. - Structured individual module directories (e.g., `src/autocomplete`, `src/dialog`) to expose components cleanly. - Added comprehensive [index.ts](cci:7://file:///c:/Users/adity/Desktop/Coding%20Side/m3e/packages/react/src/index.ts:0:0-0:0) and `all.ts` aggregators for straightforward consumption by end users in SSR environments.
commit: |
Owner
|
Closing this as it's no longer needed (see #26). |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…. Implement dynamic Next.js client-side wrappers for all components.
Closes #26
dynamicimports with"use client"directives for all@m3e/reactcomponents.M3eDialogAction,M3eListItem, etc.) to ensure strict type compliance.src/autocomplete,src/dialog) to expose components cleanly.all.tsaggregators for straightforward consumption by end users in SSR environments.Description
This PR introduces comprehensive Next.js wrappers for all
@m3e/reactcomponents to ensure seamless integration in Next.js applications, specifically targeting SSR compatibility.I've manually created structured directories for each component (e.g.,
src/autocomplete,src/dialog, etc.) and mapped their respective subcomponents (likeM3eDialogAction,M3eListItem). Each component is meticulously exported as a client-side component using Next.jsdynamic()imports and the"use client"directive, while strictly maintaining type compliance with the underlying@m3e/reactlibrary.Additionally, index.ts and all.ts files have been implemented to act as an aggregator, allowing end-users to import robust, client-ready components directly from
@m3e/nextjs.Related Issue
Closes #26
Type of Change
Checklist
Screenshots (if applicable)
Additional Notes
All TypeScript interfaces and exports have been verified, and the
npm run buildprocess completes cleanly. The Next.js package is now internally structured and ready for use.