Build Process
When you deploy, Weldship builds an optimized production bundle of your application. Understand the build process to troubleshoot issues and optimize performance.
Build Steps
- Validation - Code is checked for errors
- Bundling - JavaScript is bundled and tree-shaken
- Optimization - Assets are minified and compressed
- Image Processing - Images are optimized for web
- Static Generation - Pages are pre-rendered where possible
- Upload - Files are uploaded to CDN
Build Time
Typical builds take 1-3 minutes depending on:
- Project size and complexity
- Number of pages and components
- Image count and sizes
- Dependencies and packages
Build Credits
Build time consumes credits based on duration. Larger projects use more credits. Check your usage in the billing section.
Build Output
The build produces:
- HTML - Pre-rendered pages
- JavaScript - Client-side bundles
- CSS - Optimized stylesheets
- Assets - Images, fonts, and other files
Automatic Optimizations
- Code splitting - Only loads necessary code
- Tree shaking - Removes unused code
- Minification - Compresses JavaScript and CSS
- Image optimization - Converts to modern formats
- Lazy loading - Defers loading of off-screen content
- Caching - Aggressive CDN caching for performance
Handling Build Errors
If a build fails:
- Check the build logs for error messages
- Review recent changes that might have caused issues
- Use the AI chat to help fix errors
- Try building again after fixes
Failed Builds
Failed builds don't affect your current live deployment. Your existing production site stays up while you fix issues.
Next Steps
- Status Tracking - Monitor builds
- Logs - View detailed logs