The open-source frontend for any eCommerce. Built with a PWA and headless approach, using a modern JS stack. We have custom integrations with Magento, commercetools, Shopware and Shopify and total coverage is just a matter of time. The API approach also allows you to merge VSF with any third-party tool like CMS, payment gateways or analytics. Newest updates: https://blog.vuestorefront.io. Always Open Source, MIT license.
PM2 requires ts-node instead of running purely on the built code from dist
Expected behavior
I can build the project with dev dependencies, install prod dependencies only, move the full artifact to the prod server and run the app without any building
Steps to reproduce the issue
See how ecosystem.json and package.json are configured
Can you handle fixing this bug by yourself?
[x] YES
[ ] NO
Which Release Cycle state this refers to? Info for developer.
Pick one option.
[x] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.
Additional information
I marked it as to develop because it should be fixed in 2.0 rather than 1.11 due to major potentially breaking changes
Current behavior
PM2 requires ts-node instead of running purely on the built code from
dist
Expected behavior
I can build the project with dev dependencies, install prod dependencies only, move the full artifact to the prod server and run the app without any building
Steps to reproduce the issue
See how ecosystem.json and package.json are configured
Can you handle fixing this bug by yourself?
Which Release Cycle state this refers to? Info for developer.
Pick one option.
develop
branch and create Pull Request2. Feature / Improvement
back todevelop
.release
branch and create Pull Request3. Stabilisation fix
back torelease
.hotfix
ormaster
branch and create Pull Request4. Hotfix
back tohotfix
.Additional information
I marked it as to develop because it should be fixed in 2.0 rather than 1.11 due to major potentially breaking changes