Known tools issues

Adding a new package might result in issues while fdt editor run is running. Rerun fdt editor run after adding the package to resolve them.

There's a known issue with adding or deleting files while fdt editor run is running. It occurs when the addition or deletion causes a file override, e.g. when you add packages/my-package/src/install.js while packages-shared/my-package/src/install.js already existed before running fdt editor run. This issue prevents a cache from being invalidated for the file, meaning the build will still include the already existing (overridden) file and not the newly added file. Rerunning fdt editor run resolves this issue.

It's possible that fdt editor run is not picking up changes made to configuration. This might be due to your system running out of file watch handles because your system is trying to watch too many files. This might occur when, for example, you're running multiple fdt editor run processes combined with several Visual Studio Code instances. Reducing this should free up file watch handles, and should start to pick up changes again as a result.

In addition, watching files or directories can be unreliable, and in some cases impossible, on network file systems (NFS, SMB, etc.) or host file systems when using virtualization software such as Vagrant or Docker.

There's a known issue with using Git Bash for Windows. When running or , the add-on selection does not render properly and does not handle input keys correctly due to the fact that Git Bash is not an interactive/TTY terminal.

A workaround for this issue is to:

• Use Windows Powershell, Command Prompt or any other interactive/TTY terminal to run the commands to initialize or upgrade an editor.

• Use --non-interactive and when initializing or upgrading an editor. The downside is that you would need to know the add-on names beforehand. See the add-ons API documentation for a list of names.