🚧 Let's STEAM - MicroPython Editor (experimental) 🚧
This is a simple experimentation to use MicroPython on the STM32L475 board (and STM32WB55 later ?).
Link to test : https://letssteam.github.io/micropython-editor-experimental/
- Node.JS (>= 12.x)
- NPM (>= 7.5.2)
--watch
: recompile after editing a file (static file or Typescript file)--release
: Minify files for production
- Clone this repository
git clone https://github.com/letssteam/micropython-experiments.git
- Run
npm install
- Run
gulp
to compile and produce the static website indist
folder
Pro tip Usegulp --watch
to recompile after editing a file ! - Run a simple HTTP server on
dist
folder (exemple:python3 -m http.server
)
Only if MicroPython is already flash on the target
When you flash the target with the generated hex
file, ALL the data in the target can (will) be erased. When you use the editor to flash your python program, only the python files will be overwritten.
This editor use WebUSB to flash or send programme directly from your browser to the target. BUT this is ONLY available on chrome based browser (Chrome, Chromium, Brave, Edge, etc)
On any other browser, neither the first two buttons (connect and flash) nor the serial output (on the right of the screen) appear.
All the vulnerabilities found by npm audit
are for dev dependencies, only. I let you read this excellent article (https://overreacted.io/npm-audit-broken-by-design/), that explain why npm audit
is not...ideal.
THIS IS EXPERIMENTAL, please be kind ❤️