nextjs-starter-medusa VS strapi-medusa-template

- 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.

# using npx npx create-strapi-app strapi-medusa --template https://github.com/Deathwish98/strapi-medusa-template.git # using yarn yarn create strapi-app strapi-medusa --template https://github.com/Deathwish98/strapi-medusa-template.git