steps:
npm install -g yo
npm install -g grunt
npm install -g bower
npm install -g generator-angular
mkdir storefront
cd storefront/
yo angular
grunt serve
grunt serve isn't working for me as seen below:
ME$ grunt serve
Running "serve" task
Running "clean:server" (clean) task
>> 0 paths cleaned.
Running "wiredep:app" (wiredep) task
Running "wiredep:test" (wiredep) task
Running "wiredep:sass" (wiredep) task
Running "concurrent:server" (concurrent) task
Warning: Running "compass:server" (compass) task
Warning: Couldn't find the `compass` binary. Make sure it's installed and in your $PATH Use --force to continue.
Aborted due to warnings.
Execution Time (2015-04-08 20:14:01 UTC)
loading tasks 5ms ▇▇▇▇▇▇▇▇▇▇ 21%
compass:server 18ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 75%
Total 24ms Use --force to continue.
Aborted due to warnings.
Execution Time (2015-04-08 20:13:58 UTC)
wiredep:app 115ms ▇▇▇▇ 4%
concurrent:server 2.6s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 95%
Total 2.8s
I tried two things:
sudo npm install -g grunt-cli
that resulted in:
$ sudo npm install -g grunt-cli
Password:
/usr/local/bin/grunt -> /usr/local/lib/node_modules/grunt-cli/bin/grunt
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/module-deps/node_modules/through2 requires readable-stream#'~1.0.17' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.27-1
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/phonegap-build requires colors#'0.6.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream#'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
grunt-cli#0.1.13 /usr/local/lib/node_modules/grunt-cli
├── resolve#0.3.1
├── nopt#1.0.10 (abbrev#1.0.5)
└── findup-sync#0.1.3 (lodash#2.4.1, glob#3.2.11)
and
npm install -g compass
that resulted in:
ME$ npm install -g compass
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/module-deps/node_modules/through2 requires readable-stream#'~1.0.17' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.27-1
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/phonegap-build requires colors#'0.6.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream#'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
compass#0.1.1 /usr/local/lib/node_modules/compass
What is wrong?
I had the same issue. I fixed it by setting logConcurrentOutput to false in my Gruntfile.
Go to app --> Gruntfile.js
Search for concurrent, and ensure your concurrent code for logConcurrentOutput looks like this:
concurrent: {
ionic: {
tasks: [],
options: {
logConcurrentOutput: false
}
}
Related
I'm using Angular CLI: 8.3.18 for my current project. Thus, after I create a new project sudo ng new angular-reddit, I tried to install Semantic UI Component because I need to use it for styling purpose.
So, I issued this command but ended up with and error as bellow
npm i -g semantic-ui --save
The output was
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated natives#1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs#4.x.
npm WARN deprecated fsevents#1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm WARN semantic-ui#2.4.2 requires a peer of better-console#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of del#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of extend#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-autoprefixer#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-chmod#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-clean-css#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-clone#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-concat#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-concat-css#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-copy#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-dedupe#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-flatten#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-header#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-help#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-if#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-less#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-notify#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-plumber#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-print#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-rename#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-replace#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-rtlcss#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-uglify#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of gulp-watch#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of map-stream#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of replace-ext#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of require-dot-file#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of run-sequence#* but none is installed. You must install peer dependencies yourself.
npm WARN semantic-ui#2.4.2 requires a peer of yamljs#* but none is installed. You must install peer dependencies yourself.
npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /usr/local/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR! [Error: EACCES: permission denied, access '/usr/local/lib/node_modules'] {
npm ERR! stack: "Error: EACCES: permission denied, access '/usr/local/lib/node_modules'",
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/usr/local/lib/node_modules'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/narun/.npm/_logs/2019-11-10T04_12_55_741Z-debug.log
I followed the provided Url provided in console, but it still did not help solve my problem. Thanks
Firstly delete node if it is less than 10 and restart your PC
After that install node 12.13.0 atleast
Upgrade your angular cli using below command
npm install -g #angular/cli#latest
After everything is done restart your PC and then it will work
I want to install Rocket.Chat and Meteor on Freebsd 10.3
Does anyone know why when running NPM through Meteor, it is failing to download and install the modules:
[rocketchat#web ~/meteor]$ ./meteor -v
meteor: updating npm dependencies -- meteor-deque...
Building package meteor |
/usr/home/rocketchat/meteor/dev_bundle/lib/node_modules/ip-regex /index.js:3
const word = '[a-fA-F\\d:]';
^^^^^
babel-compiler: updating npm dependencies -- meteor-babel...
ecmascript-runtime: updating npm dependencies -- meteor-ecmascript- runtime...
promise: updating npm dependencies -- meteor-promise...
npm-mongo: updating npm dependencies -- mongodb...
logging: updating npm dependencies -- cli-color...
xmlbuilder: updating npm dependencies -- xmlbuilder...
Errors prevented isopacket build:
While building package meteor:
error: Can't install npm dependencies. Are you connected to the internet?
While building package babel-compiler:
error: Can't install npm dependencies. Are you connected to the internet?
While building package ecmascript-runtime:
error: Can't install npm dependencies. Are you connected to the internet?
error: File not found: .npm/package/node_modules/meteor-ecmascript- runtime/client.js
While building package promise:
error: Can't install npm dependencies. Are you connected to the internet?
error: File not found: .npm/package/node_modules/meteor-promise /promise.bundle.js
I have been trying to install arduino nodes in Node-Red through node-red-node-arduino following Node-Red's own guide (https://nodered.org/docs/hardware/arduino) to no avail. The node is marked as installed in the "Manage Palletes" tab, but it's disabled and refuses to enable itself. I tried to insert the sample code of the link above, but Node-Red doesn't recognize it. I installed the package arduino-firmata and node-red-node-serialport, and all the packages both locally (~/.node-red/node_modules) and globally (through -g option in npm), but the situation remains the same.
cd ~/.node-red
npm install node-red-node-arduino
npm install arduino-firmata
npm install node-red-node-serialport
sudo npm -g install node-red-node-arduino
sudo npm -g install arduino-firmata
sudo npm -g install node-red-node-serialport
They do spit out some weird logs, though, at least when installing locally.
> serialport#4.0.3 install /home/myusername/.node-red/node_modules/serialport
> node-pre-gyp install --fallback-to-build
[serialport] Success: "/home/myusername/.node-red/node_modules/serialport/build/Release/serialport.node" is installed via remote
/home/myusername/.node-red
├── arduino-firmata#0.3.4
├── node-red-node-arduino#0.0.9
├── node-red-node-serialport#0.4.0
└── serialport#4.0.3
npm WARN enoent ENOENT: no such file or directory, open '/home/myusername/.node-red/package.json'
npm WARN .node-red No description
npm WARN .node-red No repository field.
npm WARN .node-red No README data
npm WARN .node-red No license field.
npm WARN In serialport#4.0.3 replacing bundled version of minimist with minimist#0.0.8
npm WARN In serialport#4.0.3 replacing bundled version of abbrev with abbrev#1.0.9
npm WARN In serialport#4.0.3 replacing bundled version of delegates with delegates#1.0.0
...
Here is the log that shows up when running node-red in the terminal.
[warn] [arduino] Error: Cannot find module 'firmata/node_modules/serialport'
I have a Meteor + React app that works fine locally. I've tested using the --production flag and there are no issues.
Once I use mupx to deploy to my server, the deployment is successful but when I go to the deployed app it throws "There is no route for the path: /".
My routes.js file is located in the client directory.
Here is my mupx logs -f result
npm WARN deprecated This version of npm lacks support for important
features, npm WARN deprecated such as scoped packages, offered by the
primary npm npm WARN deprecated registry. Consider upgrading to at
least npm#2, if not the npm WARN deprecated latest stable version. To
upgrade to npm#2, run: npm WARN deprecated npm WARN deprecated npm -g
install npm#latest-2 npm WARN deprecated npm WARN deprecated To
upgrade to the latest stable version, run: npm WARN deprecated npm
WARN deprecated npm -g install npm#latest npm WARN deprecated npm
WARN deprecated (Depending on how Node.js was installed on your
system, you npm WARN deprecated may need to prefix the preceding
commands with sudo, or if npm WARN deprecated on Windows, run them
from an Administrator prompt.) npm WARN deprecated npm WARN
deprecated If you're running the version of npm bundled with npm WARN
deprecated Node.js 0.10 LTS, be aware that the next version of 0.10
LTS npm WARN deprecated will be bundled with a version of npm#2, which
has some small npm WARN deprecated backwards-incompatible changes made
to npm run-script and npm WARN deprecated semver behavior. npm WARN
package.json meteor-dev-bundle#0.0.0 No description npm WARN
package.json meteor-dev-bundle#0.0.0 No repository field. npm WARN
package.json meteor-dev-bundle#0.0.0 No README data
fibers#1.0.8 install
/bundle/bundle/programs/server/node_modules/fibers node build.js ||
nodejs build.js make: Entering directory
/bundle/bundle/programs/server/node_modules/fibers/build' CXX(target)
Release/obj.target/fibers/src/fibers.o CXX(target)
Release/obj.target/fibers/src/coroutine.o CC(target)
Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target)
Release/obj.target/fibers.node SOLINK_MODULE(target)
Release/obj.target/fibers.node: Finished COPY Release/fibers.node
make: Leaving
directory/bundle/bundle/programs/server/node_modules/fibers/build'
Installed in
/bundle/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node
npm WARN cannot run in wd meteor-dev-bundle#0.0.0 node npm-rebuild.js
(wd=/bundle/bundle/programs/server) ansi-regex#0.2.1
node_modules/ansi-regex
ansi-styles#1.1.0 node_modules/ansi-styles
escape-string-regexp#1.0.5 node_modules/escape-string-regexp
chalk#0.5.1 node_modules/chalk
has-ansi#0.1.0 node_modules/has-ansi
strip-ansi#0.3.0 node_modules/strip-ansi
supports-color#0.2.0 node_modules/supports-color
eachline#2.3.3 node_modules/eachline
type-of#2.0.1 node_modules/type-of
amdefine#1.0.0 node_modules/amdefine
asap#2.0.3 node_modules/asap
underscore#1.5.2 node_modules/underscore
meteor-promise#0.5.1 node_modules/meteor-promise
promise#7.0.4 node_modules/promise
source-map-support#0.3.2 node_modules/source-map-support
semver#4.1.0 node_modules/semver
source-map#0.1.32 node_modules/source-map
fibers#1.0.8 node_modules/fibers
=> Starting meteor app on port:80
I created a bundle and try install as wrote in readme
> node ./build.js
module.js:340
throw err;
^
Error: Cannot find module '/root/bundle/programs/server/node_modules/fibers/build.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
npm ERR! fibers#1.0.1 install: `node ./build.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the fibers#1.0.1 install script.
npm ERR! This is most likely a problem with the fibers package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./build.js
npm install -g fiders works as well
I'm not sure if this is the same problem, but starting with 0.9.0 you have to install fibers after unpacking the build. From the readme:
To prepare a bundle created with meteor bundle for execution on a server, you now run npm install with no arguments instead of having to specify a few specific npm modules and their versions explicitly. See the README in the generated bundle for more details.
I do something like this in my deployment script:
meteor bundle /path/to/target/bundle.tgz
cd /path/to/target/
rm -rf bundle
tar xzf bundle.tgz
cd bundle/programs/server && npm install