magento2-vsbridge-indexer VS hilla

Vue Storefront ironically just released React support and could be a great way solution to build off of — and it's totally backend agnostic

https://vuestorefront.io and https://github.com/ittus/vuejs-slack-clone-realtime

Vue Storefront differs from the other headless digital commerce solutions in that it’s written in vue.js and can be connected to any eCommerce platform. As an open-source frontend framework, it helps you curate customer experience, including PWA and offline functionalities.

Vue store front is also an option for e-commerce. https://vuestorefront.io

Vue Storefront was built by Bartłomiej Roszkowski, Filip Rakowski, Patrick Friday in 2017. It's an open source frontend framework written in vue.js that can be connected to any eCommerce platform.

The project was to build a kid's clothing store. We were writing the backend in Node.JS to communicate in Magento and the frontend in Vue storefront. Turns out that the other team had been working on the backend only for the last month, and the frontend is basically the default storefront installation. There's a demo in three days, and the VC will be presenting the demo himself. He says, "I'll show them the default Vue Storefront UI itself. They won't understand." Not sure if Vue Storefront has changed in the last four years or if we had changed something, but the default installation was a clothing store (Seems to be still the case, except UI was different.), so we were half good.

I am a senior web-developer and I've been playing around with new tools in the ecommerce space lately. Frameworks such as https://nextjs.org/commerce and https://vuestorefront.io/ makes it possible to easily build very custom storefronts while using Shopify or BigCommerce as a backend provider for product management and payments.

The team at Vue Storefront provides a Magento 2 module which uses Magento's native indexing functionality to index all pertinent data to ElasticSearch (ES) in a format which can be utilized by VSF. Because it hooks into the native indexing of M2, data can be automatically reindexed on Save if you wish to configure it to do so.

That will bring more issues. In vaadin flow, components are created and dom tree, data are stored in the backend. Even though it can be implemented by execution js in client, vaadin server would not be aware of changes in the dom. You will lose your data when components re-attached. Checkout https://hilla.dev instead of flow

Initially, I wanted ChatGPT to help me create Hilla applications. However, since it was trained on data up to 2021, it gave manufactured replies that did not correspond to reality.

Or maybe op is not interested in wiring up everything and just want to build the app itself? And there are a brunch of Template for this exact purpose for example Laravel Jetstream create t3 app hilla They all have all op asked for i wonder why? 🤔

You can check project hilla and get the best from the two worlds

Not at the moment. We're initially focusing on Spring Boot. There's a ticket for Quarkus support here if you want to follow it https://github.com/vaadin/hilla/issues/211.

Release blog post | Release notes