Capability log

What can Lovable actually do?

A running log of real experiments. Each question below gets tested in this project's sandbox, and the results — commands, output, and verdict — are recorded here verbatim.

Summary: what Lovable can do (so far)

Every answer on this page comes from actually running the thing in the project's sandbox — not from documentation or assumptions.

3Works
0Partially
1Fails

Context: shell, Node/Bun, and Python exist in the build-time sandbox. The deployed site runs on an edge runtime — no Python, no shell — so these tools can build and generate for the app, but the live site can't call them.

Verdict: Yes. Yes. Prettier is already part of the template, and both --check and --write run fine in the sandbox.

$bunx prettier --version
3.9.6
$bunx prettier --check "src/**/*.{ts,tsx,css}"
Checking formatting...
[warn] src/routes/index.tsx
[warn] Code style issues found in the above file.
$bunx prettier --write "src/**/*.{ts,tsx,css}"
src/routes/index.tsx 6ms  (all other files unchanged)
$bunx prettier --check "src/**/*.{ts,tsx,css}"
All matched files use Prettier code style!  exit=0
$bun run format
prettier --write .  — completed, no files left unformatted
  • prettier ^3.7.3 ships as a devDependency and package.json already defines a "format" script.
  • eslint-config-prettier and eslint-plugin-prettier are installed too, so lint and formatting do not fight.
  • The check found one real violation and --write fixed it, so the loop is genuinely usable, not just installed.
  • Adding new tools works the same way: bun add -d <pkg>, then bunx <pkg>.