Error: Can't locate the correct executable for your platform. Caused by: Cannot find package '@wasp.sh/wasp-cli-linux-x64-glibc' imported from /app/node_modules/@wasp.sh/wasp-cli/bin.jspackage.json generated in .wasp/out still contains "build": "wasp build". My old Dockerfile was calling npm run build, which triggers the Wasp CLI inside the container, but it fails to find its platform-specific binary (or glibc)..wasp/out still has a "build": "wasp build" script?wasp build locally, I assume I shouldn't be running wasp commands inside the container. Given the new directory structure, should my custom Dockerfile just call npm install and then npm run bundle inside the server/ directory instead of calling the root build script?@wasp.sh/wasp-cli dependency during deployment?Join the Discord to ask follow-up questions and connect with the community
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.
4,603 Members
Join