The Particle CLI compile command is slow in comparison to Workbench’s Compile application (local) command.
which CLI command are you running exactly?
...is it possible to call the make command directly?
assuming you are in VSCode, you can run the Particle: Launch Compiler Shell command. not the most elegant api though
what @ScruffR says is accurate. i'd just add that Workbench's local compiler also caches artifacts between builds so after the 1st run things go much faster. downside is sometimes it gets confused by the old cache data, spits out a weird error, and you need to reset things via cleaning (see the Particle: Clean application & DeviceOS (local) task for example).
Sorry for the late reply. Been out for the past week.
I’m running particle compile bseries. I think I see whats happening. When I disconnect from the Internet entirely Workbench (VS Code) has no troubles. Compiles the code within a couple/few seconds. But when running the CLI it spits an error, “Compile failed: getaddrinfo ENOTFOUND api.particle.io”. So, its trying to phone home.
That would explain it for me. In the shop sometimes the WiFi can be terrible. The slow down is likely that its just network slowdown. Is there a way to disable any Internet call entirely?
(vim is my main editor, thats why I’m looking for a solution outside of VS Code)