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

[Idea]: Inertia JS 2.0 support #36

Open
1 task done
hamburger-fries opened this issue Jan 19, 2025 · 1 comment
Open
1 task done

[Idea]: Inertia JS 2.0 support #36

hamburger-fries opened this issue Jan 19, 2025 · 1 comment
Assignees

Comments

@hamburger-fries
Copy link

Contact Details

[email protected]

What would this feature do?

I would like to see InertiaJS 2.0 so that we could make ReactJS apps.

I make inertiaJS + ReactJS plugins in a Monolithic format instead of Headless. This allows me to do massively.y more advanced coding. I made a microservices plugin with ReactJS components that include golang libraries. For example I use https://github.com/lesismal/nbio for a ReactJS chat component. Both my mobile React native apps use the same websocket library and related API's so that the Wordpress plugin can interact. If there was a tighter integration with Structeezy and InertiaJS I could make Bricks Builder themes more easily for my plugins. Currently I have to make separate themes and cant use Bricks builder for plugin templates.

Structeezy could be a Hybrid Bridge between headless and monolithic.

What would be this feature settings?

I suppose a setting with a toggle - on /off. Also could be form fields for directory for extra libraries. I think we would need to experiment.

I am happy to help you code this.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@cbontems
Copy link
Contributor

Hello @hamburger-fries,

Thanks for the suggestion. I haven't used InertiaJS a lot, so I will have to dig a little more into it to assess the potential impact.

Structeezy is a React app but currently doesn't load anything on frontend. Such a feature would probably imply creating a custom element for creating the Inertia App root and loading the library, similar to the AlpineJS libraries manager custom element.

But this would still need external compilation for the App, right? Or do you have something else in mind ?

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

2 participants