distributions VS Pinout.xyz

The npx install playwright install when run inside the official docker container installs node 18 version. Since last few weeks node 18/20 installation is failing on few Linux distributions - nodesource/distributions#issues/1576.

Hello guys! I want to say first that this problem is caused by me. So I kind of know when it append. I will try to explain what's my problem. Basically, any time I try to install with apt or deb packages, there is an error. This happend after I installed node js with https://github.com/nodesource/distributions. Now every time that I install something it fails. The other problem for me is that i'm not english and my os is in french. The thing is, i can't juste copy/paste the errors because there's no result in Google. I tried to find a way to get the error message in english but it did not worked. I'm not used to it but I would like help. So If anyone knows what the problem could be this would be incredible. Thanks!

Node will be the next step, using setup code made from this open-source repository (can also choose a different version of Node/npm):

This is now fixed: https://github.com/nodesource/distributions/issues/1507#issu...

Lets now install npm and Node.js which we are definitely going to need for installing JavaScript packages. You can find the latest versions of Node.js here https://github.com/nodesource/distributions/blob/master/README.md

The NodeSource Node.js distributions repository contains information both about supported versions of Node.js and supported Linux distributions. To learn more about usage, see the repository: https://github.com/nodesource/distributions

Obligatory shameless plug of https://pinout.xyz where I’ve been maintaining an interactive Raspberry Pi SBC pinout for some years, and the newer https://pico.pinout.xyz where I’ve tried to do the same for the Raspberry Pi Pico board. The latter also became a command-line pinout via the Python package “picopins”

I feel- and of course I’m biased- that if anything is worth bringing to the table for device pinouts it’s interactivity and accessibility. The latter, in particular, is lost in static images. I really leaned into this with the Pico Pinout, including everything from visual accessibility accommodations (avoiding low contrast text background colours), to markup for screen readers to the ability to turn off labels and reduce noise. I’m still unsure if I actually achieved my goal, but it’s been fun.

There is a great resource to be found at pinout.xyz that details a lot of boards and the pins they actually use.

All the LEDs have their negative pins together and go through two 1k resistors in series on their way to ground (any gpio ground pin). Then a short piece of jumper wire goes from the positive lead of each LED to it's GPIO pin number. Don't use the pin order number, use the GPIO number.

I wanted to create an accessible alternative to the official Pico pinout image, offering more complete pin details, light/dark modes, screen-readable text, and at least some capacity to focus on the peripherals you’re interested in. It’s a sister site to the now ancient Raspberry Pi pinout (https://pinout.xyz/) which started out life hosted on a Raspberry Pi.

GPIO PIN numbers - its a real pain with both board and BCM numbers (see pinout.xyz for details) without having to translate what the libraries use by default!

The pins are at top right corner here: https://pinout.xyz/ and you just connect TX to RX, RX to TX and GND to GND. On the software side you can use picocom on the builtin serial device. Not sure which though, seems to depend on the software and exact revision of your RPi.

You can see all the pins on the pin documented at https://pinout.xyz

Use pinout.xyz to see what pins are used for the SPI interface on your Pi.

You have mixed up the PIN numbers - the Pi has two sets on numbers (board and BCM) - see here for details