Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Documentation for shared ModuleRegistry setup in Next.js applications #1

Open
sina-ss opened this issue Feb 4, 2025 · 0 comments

Comments

@sina-ss
Copy link

sina-ss commented Feb 4, 2025

First, I want to thank you for providing comprehensive examples for AG Grid integration with various frameworks. The examples have been incredibly helpful in getting started with AG Grid.

However, I've noticed that in the Next.js examples, the ModuleRegistry and LicenseManager are initialized separately for each grid component. This approach can be problematic when dealing with multiple grids in a single application, which is a common use case for many websites.

For example, in a dashboard application, you might have:

  • A data grid showing user activity
  • Another grid displaying transaction history
  • A third grid showing system logs

Currently, each grid component would need to initialize its own ModuleRegistry and LicenseManager, which isn't ideal for maintaining a single source of truth and could potentially lead to initialization conflicts.

Could you provide guidance or update the documentation to show the recommended approach for:

  1. Setting up a shared ModuleRegistry that can be used across multiple grid instances
  2. Initializing the LicenseManager once for the entire application
  3. Properly handling this setup specifically in the Next.js app router environment

This would be particularly valuable for enterprise applications where multiple grids are the norm rather than the exception.

Thank you for your consideration!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant