Please keep the "mailing" list in the reply list.
I'm not "HERE" to support "YOU".. I'm "HERE" to support the "GROUP"...
On Wed, Jul 4, 2018 at 9:21 AM, Ichrak Mansour
<
ichrakma...@gmail.com> wrote:
> This is the result of this command :
>
> root@beaglebone:/home/debian# sudo /opt/scripts/tools/version.sh
> git:/opt/scripts/:[31292bce1d4b35b497cc7a013d6d57e7e1f4f5c4]
> eeprom:[A335BNLT BBG115094493]
> model:[TI_AM335x_BeagleBone_Green]
> dogtag:[BeagleBoard.org Debian Image 2018-06-17]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2018.03-00002-gac9cce7c6a]:[location: dd MBR]
> kernel:[4.14.49-ti-r54]
> nodejs:[v10.5.0]
Ah you upgraded to nodejs v10!!! You broke it...
Currently in debian 9.x "I" have built cloud9 for nodejs v6 (by
default) and v8 (for a future migration option)..
So yeah, in our debian 9.x images, if you upgrade the default nodejs
v6 to v7, v8, v9, v10, vNEXT, cloud9 will break catastrophically.
What you are experiencing is a major pain in the ass of nodejs, every
major revision is in-compatible with previously built nodejs projects.
If you need nodejs v10 "today" feel free to use the buster image:
https://rcn-ee.net/rootfs/bb.org/testing/2018-07-02/