Error staring spatialmap

[lgatto]

Since a couple of commits ago, I can't run spatialmap anymore

$ npm run start

> react-boilerplate@3.4.0 start /home/lg390/dev/SpatialMapDev
> cross-env NODE_ENV=development node server

sh: 1: cross-env: Permission denied

npm ERR! Linux 3.13.0-107-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "start"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! react-boilerplate@3.4.0 start: `cross-env NODE_ENV=development node server`
npm ERR! Exit status 126
npm ERR! 
npm ERR! Failed at the react-boilerplate@3.4.0 start script 'cross-env NODE_ENV=development node server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-boilerplate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=development node server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-boilerplate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-boilerplate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/lg390/dev/SpatialMapDev/npm-debug.log

There's also this, but not sure if relevant

 UNMET PEER DEPENDENCY webpack@2.2.0-rc.3

@Kohze - any idea?

[Kohze]

I will check the status entries and look if I can change anything (and write you back tomorrow). The only larger change (that could disrupt the start itself) I did was adding the package to the git (instead of gitignore) to include my modifications for the profile plot.

[Kohze]

I looked a bit around, some posts suggest a "npm rebuild" for the "cross-env permission denied" while others say its the typical chmod 777 permission denied linux problem (were one can recursively change order permissions). In every case I need to fix the problem since the webserver will face the same problem.

[lgatto]

An npm rebuild (after pulling) enables to start the server again, but now the datasets page stalls:

I can also see this warning, in case it helpful

% npm run start

> react-boilerplate@3.4.0 start /home/lg390/dev/SpatialMapDev
> cross-env NODE_ENV=development node server

Server started ! ✓

Access URLs:
-----------------------------------
Localhost: http://localhost:3000
      LAN: http://192.168.0.3:3000
-----------------------------------
Press CTRL-C to stop

(node:3663) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
webpack built b56d79fadee0dce1e95a in 8334ms

[Kohze]

I get the same warning while the datasets page is loading http://prntscr.com/h49og5

But it might be related to the changes I recently did to the upload process and thereby the metadata structure (Involves the private/public data). I will have a closer look into it.

[Kohze]

Ok lets first test if the firebase connection is the source of the problem (and the connection is denied in the first place): http://localhost:3000/dataView/-Km13xp504HfeCFElQFO

If the page opens (after starting the server), the can exclude that possibility. Otherwise I would need a console error log (in chrome its "rightclick" -> "inspect" -> "console tab" ) to see generally if any browser errors are reported (http://prntscr.com/h73ao9 example how it looks).

[lgatto]

git reset --hard
git pull
npm install --save
npm run start

fails with

> react-boilerplate@3.4.0 start /home/lg390/dev/SpatialMapDev
> cross-env NODE_ENV=development node server

sh: 1: cross-env: Permission denied

npm ERR! Linux 3.13.0-107-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "start"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! react-boilerplate@3.4.0 start: `cross-env NODE_ENV=development node server`
npm ERR! Exit status 126
npm ERR! 
npm ERR! Failed at the react-boilerplate@3.4.0 start script 'cross-env NODE_ENV=development node server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-boilerplate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=development node server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-boilerplate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-boilerplate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/lg390/dev/SpatialMapDev/npm-debug.log

If I try to install react-boilerplate

$ npm install --save react-boilerplate
npm ERR! Linux 3.13.0-107-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "--save" "react-boilerplate"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ENOSELF

npm ERR! Refusing to install react-boilerplate as a dependency of itself
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/lg390/dev/SpatialMapDev/npm-debug.log

I probably have a rather old version of npm, as my OS is a bit old

$ npm --version
3.10.10

Any suggestion?

[Kohze]

Im running npm 4.2.0 but i cant imagine that causes the error. I will setup the server on a fresh linux install to figure out if there is a general issue or just package dependency/permission problems.

[lgatto]

Ok, thanks. Let me know.