nextjs-starter-medusa VS Svelte

- Bug finding/reporting

You can see a case study of some past work I've done with Automatisch.io helping build their E2E test suite and other QA work here

- https://qacomet.com/case-studies/automatisch

Also, I am currently working with MedusaJS helping get their template project ready with a suite of automated tests. Some example bug reports include

- https://github.com/medusajs/nextjs-starter-medusa/issues/295

Like Medusa, the Next.js Starter is fully open source. Check out the live demo or get the code on GitHub.

Yes, check out this one: https://next.medusajs.com/ - all source code for it is open sourced

Visit the hosted demo of the template. Or, learn how to set it up in our Docs.

Thanks. I know we shouldn't care about re-render if there is no performance issue. But I still think that we need to memoize the value of context if we have other states in the provider that isn't included in the value. For example, in this provider, we have a custom hook. When it re-renders, the provider re-renders as well. That creates a new value object and all consumers re-render.

Unique Admin Interface: Medusa offers an easy-to-use admin interface where merchants can manage their products, customers, and sales records and maintain their e-store. Medusa also offers a ready-to-use storefront.

npx create-next-app -e https://github.com/medusajs/nextjs-starter-medusa b2b-storefront

View on GitHub

Now that you have every backend component ready, you need to take care of the storefront. You can build a whole storefront yourself but for this tutorial, you’ll use the official Next.js Starter provided by Medusa.

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.