You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just documenting this, it's not a big one to fix, but will be needed for prod in the future. I know that prod is not a ready-to-use thing as of now, but maybe someone comes across this issue. I'm evaluating the performance of Medusa right now which is why I care about production already. The current prod Dockerfile uses an npm installation which excludes devDependencies: https://github.com/medusajs/docker-medusa/blob/main/backend/Dockerfile.prod#L41
However, when running using the develop.sh script with the "run" parameter (which is the Dockerfile entrypoint), babel is started too:
Fix for now: run an npm i instead of npm i --only=production.
The text was updated successfully, but these errors were encountered:
Just documenting this, it's not a big one to fix, but will be needed for prod in the future. I know that prod is not a ready-to-use thing as of now, but maybe someone comes across this issue. I'm evaluating the performance of Medusa right now which is why I care about production already. The current prod Dockerfile uses an npm installation which excludes devDependencies:
https://github.com/medusajs/docker-medusa/blob/main/backend/Dockerfile.prod#L41
However, when running using the develop.sh script with the "run" parameter (which is the Dockerfile entrypoint), babel is started too:
Fix for now: run an
npm i
instead ofnpm i --only=production
.The text was updated successfully, but these errors were encountered: