Below are some quick fixes to help you troubleshoot some common issues in the development environment.

No space left on device

Sometimes Yarn cache runs wild and pollutes the disc space in your Frontastic sandboxFrontastic sandbox - A virtual machine hosted in the cloud that you can use for backend and some frontend development. They're provisioned from the developer area of the Frontastic studio. or the logs run full due to a high error rate. To clean it up, destroy your sandbox in the Frontastic studioFrontastic studio - The interface you use to manage, build, and edit all areas of your project and commerce sites. Previously known as `backstage`. and create a new one.

Symfony doesn't pick up my changes

In some cases, Symfony doesn't pick up changes (for example, when you created a new bundle).

Firstly, clear your Symfony cache the standard way:

$ bin/console cache:clear

If that doesn't work, you can try force deleting the cache on the disk:

$ rm -r /var/cache/frontastic/<project>/dev/*

Here <project> is the directory name of the project you are working with.

You can also clear all caches with a single command at once:

$ rm -r /var/cache/frontastic/*/*/*


If you happen to delete some of the directories on the way of this path, you might run into trouble that these directories are missing afterward. ant prepare will fix this for you.

High load when provisioning under Windows

While provisioning, Yarn will install node packages and their dependencies. Node packages consist of many small files and every file has to be inspected by Windows Defender for malware and indexed by the Windows Search Index. This puts a high load on the system and isn't useful for node packages.

You can exclude the project directory from Windows Defender and Windows Search Index to get better performance.

Did this page help you?