Quick Setup

First install the frontend dependencies.
Then install the Tauri Cli, and launch the project using your preferred dependency manager :

npx tauri dev
yarn tauri dev
pnpm tauri dev
cargo tauri dev

Advanced setup

Unfortunatly, TauriCli does not support cargo env (see this issue).
To use the following features, you need to start tauri and the frontend separately with pnpm start and cargo run

Update the frontend JSON

The frontend JSON is rebuilt with each tauri launch.
You can configure the input file with the SATISFACTORY_JSON variable in .cargo/config.toml.
It can be an absolute path, or a relative path to src-tauri/assets/, and the file must be encoded in UTF-8. You can find these JSON files in the game folder (Satisfactory\CommunityResources\Docs), but they are encoded with UTF16-LE and must be reencoded before use.

Updating the icons

You can extract these icons from the game files using FModel, and following a guide like this one.
Please note that the guide is a little outdated and that the UE Version you should use is GAME_UE5_3.

To export the icons needed, select the archive FactoryGame-Windows.utoc. Then navigate to FactoryGame/Content/FactoryGame/Resource, right click on the folder and select Save Folder's Packages Textures (.png).
Wait until the line [INF] Successfully saved FactoryGame/Content/FactoryGame/Resource appear in the console.

You can now set the SATISFACTORY_EXPORT_DIR variable in .cargo/config.toml with the value "{{absolute path to the output folder}}\\Exports\\FactoryGame\\Content".
The icons will be extracted with each tauri launch.

Inspirations

ngx-vflow for the node base editor

Ficsit Companion for the features