fix: configure Vercel output directory #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ungden
commented
Dec 5, 2025
ungden
commented
- Add vercel.json to specify correct build command and output directory
- Set outputDirectory to "public/web" where static files are generated
- This fixes the "No Output Directory named web found" error on Vercel
- Add vercel.json to specify correct build command and output directory - Set outputDirectory to "public/web" where static files are generated - This fixes the "No Output Directory named web found" error on Vercel
- Change buildCommand from script reference to direct command - Use 'cd packages/web/buildingai-ui && pnpm run generate' instead of 'pnpm run build:web' - Add --frozen-lockfile to installCommand for better reliability - This fixes the "Missing script: build:web" error in Vercel
- Run nuxt generate directly without release.mjs script - Change outputDirectory to packages/web/buildingai-ui/.output/public - Remove .env file dependency (use Vercel environment variables) - Set NUXT_BUILD_SSR=false and NUXT_BUILD_ENV=production inline - This fixes build exit code 1 error by avoiding release script in Vercel
- Use 'pnpm --filter @buildingai/buildingai-ui run generate' - This properly runs the generate script in the monorepo context - Output directory set to 'public/web' where release.mjs copies files - Simplified installCommand back to 'pnpm install' - This approach works with pnpm workspaces and Vercel's build environment
- Add build step for all dependencies of buildingai-ui package - Use pnpm filter with ^... to build all workspace dependencies first - Command: pnpm --filter @buildingai/buildingai-ui^... build - Then run generate to build the Nuxt app - This fixes TypeScript errors about missing @buildingai/types, @buildingai/constants, etc.
- Add build:vercel script that runs nuxt generate without --dotenv flag - Use pnpm exec for cross-env to ensure it's available in PATH - Update vercel.json to use new build:vercel script - This fixes the issue where .env file is required but not available on Vercel - Ensures public/web directory is created by release.mjs script
…ssues - Remove dependency on package.json build:vercel script - Inline entire build command directly in vercel.json - Ensures command runs correctly regardless of pnpm context - Build flow: dependencies build -> nuxt generate -> release script
- Create build-vercel.sh with full build logic - Vercel buildCommand has 256 character limit - Script handles: workspace deps build, nuxt generate, release - Update vercel.json to use: bash build-vercel.sh
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.