Neopo: A lightweight solution for local Particle development

[nrobinson2000]

UPDATE: Workbench on Pi 400 and other improvements

---

TL;DR? I’ve managed to get Particle Workbench running on my Raspberry Pi 400 by leveraging a few of the new features I’ve developed for neopo. And yes, that is the Particle debugger running.

Enhancements

• Added the neopo setup command which applies necessary tweaks to complete the installation of Particle toolchains on Manjaro x86_64 and aarch64.
• Added the neopo setup-workbench command which installs the Workbench extension pack into an existing VSCode installation and applies several tweaks to make Workbench usable on aarch64.
• Added the neopo-script command which is separate program installed in the path that functions identically to neopo script but without the overhead of importing the rest of the package. Additionally scripts can now be passed into neopo script from standard input.

Changes

• Divided neopo.py into separate files, cleaning up the codebase.
• Improved the scripting interface and the Python module API.
• Updated setup.py to provide particle, so users can easily access an encapsulated Particle CLI instance using a temporary environment that eliminates many common issues.
• Removed the neopo load command as enforcing a centralized script directory was counterproductive.

---

Installing neopo:

The following will work with most Linux distributions and macOS:

$ bash <(curl -sL neopo.xyz/install)

On Manjaro/Arch the universal installer listed above essentially does the following:

$ pacman -S --needed yay base-devel
$ yay -G neopo-git
$ cd neopo-git
$ makepkg -sif
$ neopo setup

If you are interested in using Workbench on Manjaro ARM (like I am on my Raspberry Pi 400) you can run the following to first install VSCode (if you haven’t already) and then install the Workbench extensions:

$ yay -S visual-studio-code-bin
$ neopo setup-workbench