1. For Wasp v0.15, what's the recommended way to deploy to production with Docker? Should we bundle the server code or run it directly from source? 2. In the Dockerfile, should we COPY . /app (entire project) or just COPY .wasp/build and .wasp/out/sdk? What's the minimal set of files needed? 3. When should npm run bundle happen - during wasp build, during Docker build, or at server startup?
Export/Module Questions: 4. Why does wasp build complete successfully locally, but then npm run bundle fails in Docker with "not exported by youtubeApi.ts"? Is this a Rollup configuration issue?
5. Are there specific files or directories that shouldn't be copied to Docker that might affect Rollup's ability to resolve imports? 6. For custom server code in src/server/, how does Wasp handle bundling that code along with generated code?
Architecture Questions: 7. What's the purpose of .wasp/out/sdk/ vs .wasp/build/? Which one needs to be in the Docker container for runtime?
8. Does the generated code in .wasp/build/server/src/ expect to import from the original source directory at src/server/? If so, how should Docker be set up? 9. For environment validation (validate-env.mjs), what does it actually need to access - just the SDK, or source files too?
Debugging Questions: 10. Is there a way to test/verify the bundle locally before deploying to Docker?
11. Are there known issues with Wasp v0.15 + Rollup bundling for projects with custom workers/jobs?
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.