Question 1

Why are icons missing in Lowdefy dev server but work after full build?

Accepted Answer

This is a known bug in Lowdefy 4.7.0 where the dev server's shallow build skips icon references inside page blocks. Workaround: Use lowdefy build + lowdefy start for local testing, or temporarily reference the icon in a non-page area (e.g., layout header) to force discovery. A permanent fix is in progress.

Question 2

How to select a date in Ant Design date picker using e2e helpers instead of raw Playwright?

Accepted Answer

All date picker e2e helpers now have a `do.select()` method. Use it directly: - DateSelector: `do.select('2026-03-11')` - DateTimeSelector: `do.select('2026-03-15 14:30')` (auto-selects date and time) - DateRangeSelector: `do.select('2026-03-01', '2026-03-15')` - MonthSelector: `do.select('2026-03')` If you cannot upgrade, workaround with raw Playwright: click to open, navigate months using `.ant-picker-header-prev-btn` / `.ant-picker-header-next-btn`, then click the day cell e.g., `page.locator('[title="2026-03-11"]').click()` or `.ant-picker-cell-today` for today's date.

Question 3

How to run block e2e tests using the production server instead of the dev server in Lowdefy?

Accepted Answer

Modify the createPlaywrightConfig.js in @lowdefy/block-dev-e2e. Change the webServer command from lowdefy dev to: node build --config-directory --server-directory && node start --server-directory --port --config-directory . Set serverDir to the local @lowdefy/server package (e.g., packages/servers/server). Increase timeout to 180s to allow for the production build. Ensure --config-directory is added to the start command so the CLI finds lowdefy.yaml. Existing block tests should pass without further changes.

Question 4

How to fix 'lowdefy-e2e init' template errors like wrong appDir and missing mdb fixtures import?

Accepted Answer

After running 'lowdefy-e2e init', open the generated templates and apply these fixes: 1) In playwright.config.js.template, set appDir: './' (not '../'). 2) In fixtures.js.template, replace the import with `import { mergeTests } from '@playwright/test'` and combine fixtures using `const test = mergeTests(ldfTest, mdbFixtures)` instead of `ldfTest.extend()`. Import `mdbFixtures` from `@lowdefy/community-plugin-e2e-mdb/fixtures`. 3) In example.spec.js.template, avoid navigation and page title assertions; use a health check like `await request.get('/api/auth/session')` to verify the app starts. These fixes are merged in upcoming releases—update or manually edit the templates.

Question 5

How to speed up Lowdefy Playwright e2e tests and run them in headed mode with slow motion?

Accepted Answer

To avoid cold builds (60‑90s) every run, start the dev server manually with: `lowdefy build --server e2e && lowdefy start --port 3000 --log-level warn`. Add this as an npm script (`"e2e:server"`). In `playwright.config.js`, ensure `reuseExistingServer: true` and point to `http://localhost:3000`. For headed debugging with slow motion, extend the config to support a `SLOW_MO` env var: 
```js
...config,
use: {
  ...config.use,
  launchOptions: {
    ...(process.env.SLOW_MO && { slowMo: Number(process.env.SLOW_MO) }),
  },
},
```
Then create a script: `SLOW_MO=500 playwright test --headed --workers=1 --config=e2e/playwright.config.js` (single worker avoids focus issues). These workarounds bypass the current scaffold until #2044 is resolved.

Lowdefy

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects