Linux install (maybe too early?) about gm3

[theduckylittle]

I love the enthusiasm!!!

Please check your version of NPM and Node! Minimum requirements are Node 6 and NPM 3. Here's what my local looks like (though I know older stuff works):

ducky@ThinkDuck ~ $ node --version
v7.8.0
ducky@ThinkDuck ~ $ npm --version
4.2.0

You can also checkout NVM it allows multiple version of node to be installed on a per-user basis.

[cassiel74]

mh... something is wrong here:

rmorelli@debian:~/www/gm3$ node --version
v4.7.2
rmorelli@debian:~/www/gm3$ npm --version
1.4.21

which distro are you running? I am on debian/testing

[theduckylittle]

I'm on Mint 17, however, I'm using nvm to manage my node versions. The newer versions of Node/Npm will throw warnings instead of errors as they handle peer dependencies a bit differently. I would strongly suggest using NVM (link in the post above) and install "stable."

You should also read the quickstart guide:

• https://github.com/geomoose/gm3/blob/master/docs/quickstart.md

The quickstart guide recommends creating your own fork of the gm3 repository but that isn't strictly necessary. You could instead clone geomoose/gm3 as you've already done.

[cassiel74]

I am currently using debian packages for nodejs and npm, guess I should switch to newest versions from github repos. I'll look at this stuff next week.

BTW gm3 demo looks really cool ;-)

[klassenjs]

BTW it also needs MapServer 7+ since there appears to be a WFS bug in 6.4 and older.

…

On Apr 20, 2017 7:46 AM, "cassiel74" ***@***.***> wrote: I am currently using debian packages for nodejs and npm, guess I should switch to newest versions from github repos. I'll look at this stuff next week. BTW gm3 demo looks really cool ;-) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKG9tNutaEXhnHsGHOnMRageMDUglIMks5rx1OvgaJpZM4NCmMa> .

[theduckylittle]

I'm going to Close this issue out. @cassiel74 if/when you run into another problem, please open a fresh issue