Llasas

Frequently Asked Questions

Answers to common questions about getting started, using, and extending Llasas.

Jump to First Question

Getting Started

Q: How do I install Llasas?

A: Use the CLI tool to create a new project. Run npm create llasas@latest my-app in your terminal, then navigate to the directory and start the dev server with npm start.

Q: What technologies does Llasas integrate with?

A: Llasas works seamlessly with Tailwind CSS for styling, Vite for bundling, and supports modern JavaScript features. It integrates with popular tools like ESLint and Prettier for code quality.

Q: Can I use Llasas with other frameworks?

A: While Llasas is a full-featured framework, it's designed to be modular. You can integrate components from other frameworks, but for best results, use it as a standalone solution.

Deployment & Configuration

Q: How do I deploy my Llasas app?

A: Run npm run build to create an optimized production build, then use the deploy command npm run deploy which integrates with platforms like Vercel or Netlify.

Q: Can I customize the build process?

A: Yes! You can modify the Vite config file vite.config.js to add plugins, adjust optimizations, or configure custom environments. Check the CLI documentation for advanced options.

Troubleshooting

Q: My dev server isn't starting. What now?

A: 1. Ensure Node.js 16+ is installed. 2. Check your terminal for specific error messages. 3. Delete node_modules and package-lock.json, then re-run npm install.

Q: How do I debug performance issues?

A: Use the built-in performance analysis tool by running npm run analyze. This will show a visualization of your app's bundle sizes and loading times.

Community & Support

Q: Where can I get help?

A: Join our Discord community at discord.com/llasas or view our extensive guides at /docs/guides.

Q: Can I contribute to the project?

A: Absolutely! Visit our GitHub page at /github/llasasas to open issues, submit pull requests, or contribute to documentation.

Still have questions?

Visit our documentation, jump into Discord, or create an issue on GitHub.