npm run build command initiates a comprehensive production pipeline. The framework transforms your dynamic templates into a static HTML snapshot, optimizes global assets, and generates a professional distribution archiveāeliminating the need for manual file manipulation or complex server configurations.
This ensures you have a consistent, āsealedā deliverable ready for immediate hand-off or automated deployment to the edge.
Automated Host Deployment
Squeditor features a modular, provider-based deployment system that integrates with modern static hosting platforms like Netlify and Vercel. By default, deployment is disabled to ensure builds succeed in all environments without forcing CLI installations.Configuration
Deployment settings are managed insqueditor.config.js under the deploy key where you can setup or define custom providers.
squeditor.config.js
Setup Requirements
Before enabling deployment, ensure you have the required CLI tools installed and you are logged in locally.Netlify
- Install CLI:
npm install -g netlify-cli - Login:
netlify login - First Run: Run
netlify initin your project folder once to link it to a site.
Vercel
- Install CLI:
npm install -g vercel - Login:
vercel login - First Run: Run
vercelin your project folder once to link it to a project.
Adding Custom Providers
You can extend the framework by adding custom providers to theproviders object. Each provider requires a name, a CLI command, and optional setup tips.
squeditor.config.js
Troubleshooting
If deployment fails, the build script will provide helpful hints based on the selected platform.- CLI Missing: Ensure the providerās CLI is installed globally.
- Auth Error: Ensure you are logged in (
netlify statusorvercel whoami). - Link Error: Ensure the project is linked to the platform (run
initor the base command once manually). - Manual Debug: Run the
commandspecified in your config manually in your terminal to see raw error output.