[DNG] npm and nodejs

[Hendrik Boom]

I'm trying to try out a package (joplin) that is built using nodejs.

Now the installation instructions seem to require npk, the nodejs package 
manager.

And following links about npm, it appears that npm is part of nodejs.

But I have installed nodejs from the ascii repossitory and still don't seem to 
be able to access npm.

There are some packages with npm in their names, but they look to be add-one 
for npm rather than npm itself.

Any ideas?  Is this an area where the Devuan packages are broken?  Will I have 
to go to foreign repositoories?

-- hendrik
 

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs

[wirelessduck]

> On 23 May 2018, at 11:44, Hendrik Boom  wrote:
> 
> I'm trying to try out a package (joplin) that is built using nodejs.
> 
> Now the installation instructions seem to require npk, the nodejs package 
> manager.
> 
> And following links about npm, it appears that npm is part of nodejs.
> 
> But I have installed nodejs from the ascii repossitory and still don't seem 
> to be able to access npm.
> 
> There are some packages with npm in their names, but they look to be add-one 
> for npm rather than npm itself.
> 
> Any ideas?  Is this an area where the Devuan packages are broken?  Will I 
> have to go to foreign repositoories?
> 
> -- hendrik

If you want nodejs you should install from the nodesource apt repository to get 
the latest updates.

https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

https://github.com/nodesource/distributions/blob/master/README.md

Unfortunately those instructions rely on lsb_release providing the correct 
output. There is a bug with lsb-release in ascii where it relies on parsing 
sources.list for detection.  If “lsb_release -sc” returns “ascii” then you’re 
all fine but if it returns “testing” then you’ll just have to add the repo with 
the manual instructions.

The devuan releases are aliased in the installer script to the Debian releases 
so you should just use stretch in your sources list.

—Tom

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs

[KatolaZ]

On Tue, May 22, 2018 at 09:44:11PM -0400, Hendrik Boom wrote:
> I'm trying to try out a package (joplin) that is built using nodejs.
> 
> Now the installation instructions seem to require npk, the nodejs package 
> manager.
> 
> And following links about npm, it appears that npm is part of nodejs.
> 
> But I have installed nodejs from the ascii repossitory and still don't seem 
> to be able to access npm.
> 
> There are some packages with npm in their names, but they look to be add-one 
> for npm rather than npm itself.
> 
> Any ideas?  Is this an area where the Devuan packages are broken?  Will I 
> have to go to foreign repositoories?
> 

npm was removed from Debian Stretch before it get in freeze. The
upstream provided 14 major versions in 8 months, mostly not
back-compatible. I guess the DD just gave out for good.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs

[KatolaZ]

On Wed, May 23, 2018 at 08:22:54AM +0100, KatolaZ wrote:
> On Tue, May 22, 2018 at 09:44:11PM -0400, Hendrik Boom wrote:
> > I'm trying to try out a package (joplin) that is built using nodejs.
> > 
> > Now the installation instructions seem to require npk, the nodejs package 
> > manager.
> > 
> > And following links about npm, it appears that npm is part of nodejs.
> > 
> > But I have installed nodejs from the ascii repossitory and still don't seem 
> > to be able to access npm.
> > 
> > There are some packages with npm in their names, but they look to be 
> > add-one for npm rather than npm itself.
> > 
> > Any ideas?  Is this an area where the Devuan packages are broken?  Will I 
> > have to go to foreign repositoories?
> > 
> 
> npm was removed from Debian Stretch before it get in freeze. The
> upstream provided 14 major versions in 8 months, mostly not
> back-compatible. I guess the DD just gave out for good.
   

I guess I had in mind something between "dropped out" and "gave up",
but you got the feeling... :)



-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs

[Hendrik Boom]

On Wed, May 23, 2018 at 02:44:07PM +1000, wirelessd...@gmail.com wrote:
> 
> > On 23 May 2018, at 11:44, Hendrik Boom  wrote:
> > 
> > I'm trying to try out a package (joplin) that is built using nodejs.
> > 
> > Now the installation instructions seem to require npk, the nodejs package 
> > manager.
> > 
> > And following links about npm, it appears that npm is part of nodejs.
> > 
> > But I have installed nodejs from the ascii repossitory and still don't seem 
> > to be able to access npm.
> > 
> > There are some packages with npm in their names, but they look to be 
> > add-one for npm rather than npm itself.
> > 
> > Any ideas?  Is this an area where the Devuan packages are broken?  Will I 
> > have to go to foreign repositoories?
> > 
> > -- hendrik
> 
> If you want nodejs you should install from the nodesource apt repository to 
> get the latest updates.
> 
> https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

Very unimpressed wth this installation method.  It downloads an executable and 
proceeds to execute in root mode.  Perhaps this comes naturally for those who 
write software that's meant to download and execute files in a browser, but, 
... no.

> 
> https://github.com/nodesource/distributions/blob/master/README.md

Thanks for this link.  It refers to actual deb's and signing keys.

-- hendrik

> 
> Unfortunately those instructions rely on lsb_release providing the correct 
> output. There is a bug with lsb-release in ascii where it relies on parsing 
> sources.list for detection.  If “lsb_release -sc” returns “ascii” then you’re 
> all fine but if it returns “testing” then you’ll just have to add the repo 
> with the manual instructions.
> 
> The devuan releases are aliased in the installer script to the Debian 
> releases so you should just use stretch in your sources list.
> 
> —Tom
> 

> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs

[Antonio Trkdz.tab]

Hi All,

To install the latest(ish) nodejs from nodesource get the signin keys with:

curl -sSL https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo
apt-key add -

then, after touching /etc/apt/sources.list.d/nodesource.list, add the
following to the newly created file:

deb https://deb.nodesource.com/node_8.x stretch main
deb-src https://deb.nodesource.com/node_8.x stretch main

finally install nodejs with:

sudo apt-get update
sudo apt-get install nodejs

It works for ASCII and you'll get npm.

Hope it helps.

Cheers!

Antonio

On Thu, May 24, 2018 at 4:19 AM, Hendrik Boom 
wrote:

> On Wed, May 23, 2018 at 02:44:07PM +1000, wirelessd...@gmail.com wrote:
> >
> > > On 23 May 2018, at 11:44, Hendrik Boom  wrote:
> > >
> > > I'm trying to try out a package (joplin) that is built using nodejs.
> > >
> > > Now the installation instructions seem to require npk, the nodejs
> package manager.
> > >
> > > And following links about npm, it appears that npm is part of nodejs.
> > >
> > > But I have installed nodejs from the ascii repossitory and still don't
> seem to be able to access npm.
> > >
> > > There are some packages with npm in their names, but they look to be
> add-one for npm rather than npm itself.
> > >
> > > Any ideas?  Is this an area where the Devuan packages are broken?
> Will I have to go to foreign repositoories?
> > >
> > > -- hendrik
> >
> > If you want nodejs you should install from the nodesource apt repository
> to get the latest updates.
> >
> > https://nodejs.org/en/download/package-manager/#
> debian-and-ubuntu-based-linux-distributions
>
> Very unimpressed wth this installation method.  It downloads an executable
> and proceeds to execute in root mode.  Perhaps this comes naturally for
> those who write software that's meant to download and execute files in a
> browser, but, ... no.
>
> >
> > https://github.com/nodesource/distributions/blob/master/README.md
>
> Thanks for this link.  It refers to actual deb's and signing keys.
>
> -- hendrik
>
> >
> > Unfortunately those instructions rely on lsb_release providing the
> correct output. There is a bug with lsb-release in ascii where it relies on
> parsing sources.list for detection.  If “lsb_release -sc” returns “ascii”
> then you’re all fine but if it returns “testing” then you’ll just have to
> add the repo with the manual instructions.
> >
> > The devuan releases are aliased in the installer script to the Debian
> releases so you should just use stretch in your sources list.
> >
> > —Tom
> >
>
> > ___
> > Dng mailing list
> > Dng@lists.dyne.org
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] npm and nodejs -- version skew?

[Hendrik Boom]

While setting up to run the game editor inky ( 
https://www.inklestudios.com/ink/ ) I  ran into what seems to be a version 
skew.

I used aptitude to install Devuan beowulf's versions of npm and nodejs.
When I got to one stage of the imky startup I got messages
I have appended below.

From the looks of things, npm is complaining it cannot work with node 
Node.js v10.24.0 and it wants me to "upgrade" to an *older* version! 
(namely, 4, 6, 7, 8, or 9 instead of 10..)

Is this a known problem?  Is this really a version skew between two of 
beowulf's own packages?

Somewhat hard to believe.  Is upgrading everything to chimaera likely to 
help?

-- hendrik

The messages:

hendrik@midwinter:~/dv/fun/ink/inky$ ./INSTALL_AND_RUN.command  
 
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 
7, 8, 9.
  
npm WARN npm You can find the latest version at https://nodejs.org/
npm WARN read-shrinkwrap This version of npm is compatible with 
lockfileVersion@1, but package-lock.json was generated for 
lockfileVersion@2. I'll try to do my best with it!
npm WARN notice [SECURITY] ws has the following vulnerability: 1 moderate. 
Go here for more details: 
https://www.npmjs.com/advisories?search=ws&version=7.4.5 - Run `npm i 
npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm WARN notice [SECURITY] minimist has the following vulnerability: 1 low. 
Go here for more details: 
https://www.npmjs.com/advisories?search=minimist&version=0.0.10 - Run `npm 
i npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm WARN notice [SECURITY] electron has the following vulnerability: 1 
moderate. Go here for more details: 
https://www.npmjs.com/advisories?search=electron&version=4.2.12 - Run `npm 
i npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm WARN tar write after end
npm WARN notice [SECURITY] trim-newlines has the following vulnerability: 1 
high. Go here for more details: 
https://www.npmjs.com/advisories?search=trim-newlines&version=1.0.0 - Run 
`npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to 
get more info.
npm WARN notice [SECURITY] minimist has the following vulnerability: 1 low. 
Go here for more details: 
https://www.npmjs.com/advisories?search=minimist&version=0.0.8 - Run `npm i 
npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm WARN notice [SECURITY] marked has the following vulnerability: 1 
moderate. Go here for more details: 
https://www.npmjs.com/advisories?search=marked&version=0.3.19 - Run `npm i 
npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm WARN notice [SECURITY] lodash has the following vulnerability: 1 high. 
Go here for more details: 
https://www.npmjs.com/advisories?search=lodash&version=4.17.21 - Run `npm i 
npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm WARN notice [SECURITY] diff has the following vulnerability: 1 high. Go 
here for more details: 
https://www.npmjs.com/advisories?search=diff&version=3.3.1 - Run `npm i 
npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
more info.
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! 

npm ERR! A complete log of this run can be found in:
npm ERR! /home/hendrik/.npm/_logs/2021-10-04T13_12_04_234Z-debug.log
hendrik@midwinter:~/dv/fun/ink/inky$
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs -- version skew?

[wirelessduck--- via Dng]

> On 5 Oct 2021, at 00:58, Hendrik Boom  wrote:
> 
> While setting up to run the game editor inky ( 
> https://www.inklestudios.com/ink/ ) I  ran into what seems to be a version 
> skew.
> 
> I used aptitude to install Devuan beowulf's versions of npm and nodejs.
> When I got to one stage of the imky startup I got messages
> I have appended below.
> 
> From the looks of things, npm is complaining it cannot work with node 
> Node.js v10.24.0 and it wants me to "upgrade" to an *older* version! 
> (namely, 4, 6, 7, 8, or 9 instead of 10..)
> 
> Is this a known problem?  Is this really a version skew between two of 
> beowulf's own packages?
> 
> Somewhat hard to believe.  Is upgrading everything to chimaera likely to 
> help?
> 
> -- hendrik
> 
> The messages:
> 
> hendrik@midwinter:~/dv/fun/ink/inky$ ./INSTALL_AND_RUN.command
>
> npm WARN npm npm does not support Node.js v10.24.0
> npm WARN npm You should probably upgrade to a newer version of node as we
> npm WARN npm can't make any promises that npm will work with this version.
> npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 
> 7, 8, 9.  
> 
> npm WARN npm You can find the latest version at https://nodejs.org/
> npm WARN read-shrinkwrap This version of npm is compatible with 
> lockfileVersion@1, but package-lock.json was generated for 
> lockfileVersion@2. I'll try to do my best with it!
> npm WARN notice [SECURITY] ws has the following vulnerability: 1 moderate. 
> Go here for more details: 
> https://www.npmjs.com/advisories?search=ws&version=7.4.5 - Run `npm i 
> npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm WARN notice [SECURITY] minimist has the following vulnerability: 1 low. 
> Go here for more details: 
> https://www.npmjs.com/advisories?search=minimist&version=0.0.10 - Run `npm 
> i npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm WARN notice [SECURITY] electron has the following vulnerability: 1 
> moderate. Go here for more details: 
> https://www.npmjs.com/advisories?search=electron&version=4.2.12 - Run `npm 
> i npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm WARN tar write after end
> npm WARN notice [SECURITY] trim-newlines has the following vulnerability: 1 
> high. Go here for more details: 
> https://www.npmjs.com/advisories?search=trim-newlines&version=1.0.0 - Run 
> `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to 
> get more info.
> npm WARN notice [SECURITY] minimist has the following vulnerability: 1 low. 
> Go here for more details: 
> https://www.npmjs.com/advisories?search=minimist&version=0.0.8 - Run `npm i 
> npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm WARN notice [SECURITY] marked has the following vulnerability: 1 
> moderate. Go here for more details: 
> https://www.npmjs.com/advisories?search=marked&version=0.3.19 - Run `npm i 
> npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm WARN notice [SECURITY] lodash has the following vulnerability: 1 high. 
> Go here for more details: 
> https://www.npmjs.com/advisories?search=lodash&version=4.17.21 - Run `npm i 
> npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm WARN notice [SECURITY] diff has the following vulnerability: 1 high. Go 
> here for more details: 
> https://www.npmjs.com/advisories?search=diff&version=3.3.1 - Run `npm i 
> npm@latest -g` to upgrade your npm version, and then `npm audit` to get 
> more info.
> npm ERR! cb() never called!
> 
> npm ERR! This is an error with npm itself. Please report this error at:
> npm ERR! 
> 
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/hendrik/.npm/_logs/2021-10-04T13_12_04_234Z-debug.log
> hendrik@midwinter:~/dv/fun/ink/inky$
> __

Have you tried installing Nodejs from the official apt repository?

https://github.com/nodesource/distributions/blob/master/README.md___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] npm and nodejs -- version skew?

[Hendrik Boom]

On Mon, Oct 04, 2021 at 02:25:44PM +, g4sra wrote:
> Hi Hendrik,
> 
> Are you interested in authoring some sort of game in Ink ?
> Because if you are I would be interested to hear what you are up to.

Mostly not writing a game, but trying out various game-writing engines 
to see what works and what doesn't.  An informal language-comparison 
study.

And about the version skew:

Simplest might be to look at another of the available tools before 
struggling with this one.  Of course, I'm due for an upgrade to chimaera 
soon, so if I am doomed to struggle anyway, I might as well do it with 
newer packages.

-- hendrik
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng