vendure VS nopCommerce

- https://www.vendure.io/ is a node framework so you still have to code - Strapi or other healdess CMS will allow you to create all the backend with pretty much no code. I like strapi because you can do everything from the admin panel and then if needed you can overwrite the basic api files with your own

Vendure is built-on solid foundations using TypeORM with Nest.js which allows us to define database subscribers. With a subscriber, we can listen to specific entity events and take actions based on inserts, updates, deletions and more.

After publishing Back-In-Stock Vendure plugin, we got our first issue reported almost immediately and it happened to be related to an issue with Typescript 3.7+ useDefineForClassFields flag in ts-config breaking Vendure BaseEntity initialization when consuming the plugin.

Vendure is a modern, open-source headless commerce framework built with TypeScript & Nodejs with an awesome plugin architecture to keep the monkey-business at bay.

Trust me, I've spent the past 4+ years building just that! And I'm still going. If you'd like to get a bit of an idea of what that looks like in practice, and you are happy with TypeScript & Node.js, then feel free to check out the project I maintain: https://github.com/vendure-ecommerce/vendure.

- https://github.com/vendure-ecommerce/vendure NodeJS + relational DB - https://github.com/vendure-ecommerce/storefront-remix-starter storefront built with React (Remix)

If you want to check out an example of a full-featured and mature e-commerce solution built on Node and express (actually NestJS but that also uses express internally) take a look at my project https://github.com/vendure-ecommerce/vendure. Building from scratch is a lot of work - I've been at it for the past 4 years 😅

Hi! If you like Node and TypeScript, you could check out my project, vendure.io. It handles all the typical functionality that you don't want to have to build yourself, is really customizable and is already being used by a lot of companies large and small. Recently I started a company around it to ensure it is a stable and well-maintained option for the long-term.

🔴 nopCommerce: ASP.NET Core eCommerce software. nopCommerce is a free and open-source shopping cart.

nopCommerce’s GitHub statistics:

An eCommerce website is a very complicated endeavor. Take a look at this open source eCommerce solution to see just how complicated it is.

There are two ways to deploy the app on Azure. I don't find nopCommerce in the Azure app gallery as of now though. So I have tried FTP deployment and app publishing from Visual Studio. The best way is to publish it from Visual Studio. FTP deployment takes too long to transfer files to Azure. That may be due to the app service plan, which has basic hardware performance. But the file transfer is quicker with the Visual Studio deployment. I can either clone the app from nopCommerce's GitHub site or download it from releases to do FTP deployment. To publish from Visual Studio, I need to download publish profile from Azure App Service. In Visual Studio, when you publish the app, you can just import the publish profile that you downloaded from Azure app service.

Website: https://www.nopcommerce.com/

> Can you point me to a codebase that does not use comments, as a model of how that looks in practice?

Once we actively encourage comments, this is what we get. It was totally unnecessary -

https://github.com/nopSolutions/nopCommerce/blob/develop/src...

I welcome this type of comments which state the obvious and goes beyond what the code in front of you can state -

"// If every heap's gen2 or gen3 size is less than this threshold we will do a blocking GC."

https://raw.githubusercontent.com/dotnet/runtime/main/src/co...

If you want to use with the latest .NetCore c# code you could look at https://www.nopcommerce.com which is a great open source developers platform

Learn more on the .net open-source platform's website or visit our GitHub repository

As a test I just cloned https://github.com/nopSolutions/nopCommerce