-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi not work! #16
Comments
yarn --version Module not found: Error: Can't resolve './index.css' in '/home/martin/natsboard2/nats-streaming-console/src' error Command failed with exit code 1. SyntaxError: Unexpected token ( Module not found: Error: Can't resolve './index.css' in '/home/martin/natsboard2/nats-streaming-console/src' error Command failed with exit code 1. |
sudo npm install
npm WARN deprecated react-dom@16.2.0: This version of react-dom/server contains a minor vulnerability. Please update react-dom to 16.2.1 or 16.4.2+. Learn more: https://fb.me/cve-2018-6341
npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated extract-text-webpack-plugin@3.0.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated flatten@1.0.2: I wrote this module a very long time ago; you should use something else.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated sw-precache@5.2.1: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
npm WARN deprecated sw-toolbox@3.6.0: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
Killed.............] / fetchMetadata: sill mapToRegistry uri https://registry.npmjs.org/webpack-dev-middleware
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ sudo npm run build-css
sh: node-sass-chokidar: command not found
npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "build-css"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! nats-streaming-console@1.0.2 build-css:
node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the nats-streaming-console@1.0.2 build-css script 'node-sass-chokidar --include-path ./node_modules src/ -o src/'.
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 nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ npm run build-css
sh: node-sass-chokidar: command not found
npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "build-css"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! nats-streaming-console@1.0.2 build-css:
node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the nats-streaming-console@1.0.2 build-css script 'node-sass-chokidar --include-path ./node_modules src/ -o src/'.
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 nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$ sudo npm run build-css
sh: node-sass-chokidar: command not found
npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "build-css"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! nats-streaming-console@1.0.2 build-css:
node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the nats-streaming-console@1.0.2 build-css script 'node-sass-chokidar --include-path ./node_modules src/ -o src/'.
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 nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ sudo npm run build
sh: react-scripts: command not found
npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "build"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! nats-streaming-console@1.0.2 build:
react-scripts build
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the nats-streaming-console@1.0.2 build script 'react-scripts build'.
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 nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! react-scripts build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ node server
module.js:478
throw err;
^
Error: Cannot find module 'express'
at Function.Module._resolveFilename (module.js:476:15)
at Function.Module._load (module.js:424:25)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object. (/home/martin/natsboard2/nats-streaming-console/server/index.js:2:17)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ sudo node server
module.js:478
throw err;
^
Error: Cannot find module 'express'
at Function.Module._resolveFilename (module.js:476:15)
at Function.Module._load (module.js:424:25)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object. (/home/martin/natsboard2/nats-streaming-console/server/index.js:2:17)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
[martin@myservice-pc nats-streaming-console]$
The text was updated successfully, but these errors were encountered: