Install Meteorite in Linux Using Meteor? - meteor

I need to know about install meteorite package in linux(Cent O.S) using Meteor.I'm try to using mrt & npm but i get errors like mrt not found and npm not found.I am new to meteor.So can you please suggest me how to use mrt and npm packages in Meteor?The below ones are using to install meteorite.
npm install -g meteorite
sudo -H npm install -g meteorite
The above both are get errors are npm is not found.
I'm using Ubuntu but get the below error :
[root#localhost HCare]# sudo apt-get install nodejs nodejs-dev npm
sudo: apt-get: command not found
[root#localhost HCare]#
The above both are get errors are npm is not found. And i'm using yum -y update and also get so many below messages but this is correct or not but i dont know?
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 2.4 M RSS (356 MB VSZ)
Started: Sat Mar 22 06:41:50 2014 - 3 day(s) 12:13:19 ago
State : Sleeping, pid: 6457
and also does not exit and get a lot above messages.

I would suggest using the package manager for your distribution, in this case YUM:
Install nodejs and npm: yum install nodejs npm
Install meteorite npm install -g meteorite
Since you got meteor already installed, that's it.

Related

polymer-cli installation failure on Ubuntu

No matter what I try, every time I try to install polymer-cli, it always comes up with a PERMISSION_DENIED error.
bradley#gurulaptop:~$ sudo npm -g install polymer-cli
npm WARN deprecated bower#1.8.0: ..psst! While Bower is maintained, we recommend Yarn and Webpack for *new* front-end projects! Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's no migration path but we hope you'll help us figure out one.
npm WARN deprecated #types/assert#0.0.29: See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/12826
/usr/bin/polymer -> /usr/lib/node_modules/polymer-cli/bin/polymer.js
> wd#1.2.0 install /usr/lib/node_modules/polymer-cli/node_modules/wd
> node scripts/build-browser-scripts
/usr/lib/node_modules/polymer-cli/node_modules/mkdirp/index.js:90
throw err0;
^
Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/polymer-cli/node_modules/wd/build'
at Object.fs.mkdirSync (fs.js:877:18)
at sync (/usr/lib/node_modules/polymer-cli/node_modules/mkdirp/index.js:71:13)
at Object.<anonymous> (/usr/lib/node_modules/polymer-cli/node_modules/wd/scripts/build-browser-scripts.js:6:1)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wd#1.2.0 install: `node scripts/build-browser-scripts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wd#1.2.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bradley/.npm/_logs/2017-06-06T13_10_23_400Z-debug.log
How can I solve this?
I faced the same problem and followed #Tim Lundqvist's answer and solved by the following way:
Step 1: Create a hidden folder in home. Commands:
$ cd ~
$ mkdir .polymer-patch
$ cd .polymer-patch
$ npm install polymer-cli
Step 2: create symbolic links to make it executables
$ sudo ln -s "$(readlink -f ~/.polymer-patch/node_modules/.bin/wd)" /usr/bin/wd
$ sudo ln -s "$(readlink -f ~/.polymer-patch/node_modules/.bin/polymer)" /usr/bin/polymer
$ polymer
Now polymer CLI is working for me.
Updated
This issue is node and npm version related but the following command works good
$ sudo npm install --unsafe-perm -g polymer-cli
There seems to be a problem installing the package wd as root. One way to work around this fact is to do a non global npm install of polymer-cli and use the local bin path.
$ cd ~
$ npm install polymer-cli
$ ~/node_modules/.bin/polymer --version
1.1.0
After which you may either copy all dependencies to /usr/lib/node_modules and /usr/bin/ or create symbolic links to the executables (which may be easier for a singe user system).
$ sudo ln -s "$(readlink -f ~/node_modules/.bin/wd)" /usr/bin/wd
$ sudo ln -s "$(readlink -f ~/node_modules/.bin/polymer)" /usr/bin/polymer
When the path /usr/bin/polymer exists you should be able to use the polymer command as expected.
I'm running Xubuntu, this worked
sudo npm install -g polymer-cli --unsafe-perm=true --allow-root
I got myself in the same situation. I could not install or update to the latest polymer-cli version (1.2.0). The two previous answers didn't help me at all. My solution was the downgrade of npm. I had installed:
node -v: v7.x.x
npm -v: v5.x.x
And that was the real problem.
After downgrading to npm 4.x.x by:
sudo npm install -g npm#4.1.2
I was able to install the latest polymer-cli via:
sudo npm install -g polymer-cli
Maybe you need previous also to uninstall the old wd & polymer-cli unifinished installation:
sudo npm uninstall -g wd polymer-cli
sudo rm /usr/bin/polymer
That work now for me with the tips of Tim and the same start bug after this clean up
Solved the issue: polymer-cli global install error
sudo npm install -g polymer-cli --unsafe-perm
I had the same problem, I tried different things, but what finally helped me was this:
sudo npm install -g yarn
(Consider Yarn and Webpack or Parce)

npm semver version invalid issue with grunt installation

While installing grunt, one of the errors is unmet dependency semver#4
i am using node#0.10.33, npm#1.4.28
i run two commands and it shows two versions and one is invalid
npm list -g
and in the tree it shows semver#2.3.0 invalid
now i run
npm view semver version
now it shows 4.1.0
i tried npm update semver
but nothing happens
i have even tried to the solution provided in similar question npm error invalid semver
curl https://npmjs.org/install.sh | sh
but donesnt help
I am new to npm and grunt please help!
what do you mean by While installing grunt?
Installing the grunt-cli tools or the grunt-runner in your project?
since 4.0 grunt is split into 2 modules:
grunt-cli
grunt
grunt-cli needs to be installed globally, and only 1 time:
$ npm install grunt-cli -g
grunt needs to be installed locally in every project where you want to use grunt and grunt-plugins:
$ npm install grunt
updating npm:
the crazy stuff about npm is, that you can even update npm via npm:
$ npm update npm -g
the current npm version is 2.1.9, so maybe this solves your problem.
hint: use nvm vor node.js version management. this solves multiple problems:
easy version switching
you don't need sudo for global packages

Can't install Sails.js, installation failure

When I try to install Sails.js, I get:
npm WARN deprecated grunt-lib-contrib#0.7.1: DEPRECATED. See readme: https://github.com/gruntjs/grunt-lib-contrib
npm WARN deprecated guid#0.0.12: Please use node-uuid instead. It is much better.
ws#0.4.32 install /usr/local/lib/node_modules/sails/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)
the console hangs right here and never does anything else.
I tried uninstalling all node_modules and reinstalling an earlier version:
sudo rm -rf node_modules
npm cache clear
sudo npm install npm#1.4.23 -g
sudo npm install sails -g
Still the exact same problem. Anyone else run into this and have a solution?
I had a similar problem. A better solution is to use:
npm -g install npm
This will install the latest npm version
A way of handling this, as I've seen it, is by installing the latest version of NPM:
npm install -g npm#1.4.24
And you may have to remove the Grunt Cli first done like so:
npm -g remove grunt-cli
The guys running Sails have also addressed this issue on GitHub: https://github.com/balderdashy/sails/issues/2124
I was using Mac OSX 10.7.5
I simply updated to 10.9.5 and followed the normal installation procedures, everything worked fine.
If you use apt-get or any other to install npm fist, then you must remove it with apt-get then use the sudo npm install -g npm#1.4.24 to install the 1.4 version

Upgrading Meteor: Error when running mrt migrate-app

I just upgraded Meteor to 0.9.0 and I got an error when running "mrt migrate-app".
Have I done something wrong?
-- Notice --
0.9.0: Welcome to the new Meteor package system! You can now add any Meteor
package to your app (from more than 1800 packages available on the
Meteor Package Server) just by typing 'meteor add <packagename>', no
Meteorite required.
It looks like you have been using Meteorite with this project. To
migrate your project automatically to the new system:
(1) upgrade your Meteorite with 'npm install -g meteorite', then
(2) run 'mrt migrate-app' inside the project.
Having done this, you no longer need 'mrt' and can just use 'meteor'.
All your package dependencies are already up to date.
me#ubuntu:~/myApp$ mrt migrate-app
/usr/local/lib/node_modules/meteorite/bin/mrt.js:21
throw("Subcommand " + subCommandName + " does not exist!");
First of all I did this (and it seemed to work):
me#ubuntu:/usr/local/lib/node_modules$ sudo npm install -g meteorite
First you have to update the project
meteor update
Then make sure to update meteorite
sudo npm update -g meteorite
And then run
mrt migrate-app
For more info read:
http://blog.percolatestudio.com/engineering/meteor-packaging-questions/
(Especially: How do I migrate my app from Meteorite to the Meteor Package System (0.9.0) ?)
https://hackpad.com/Migrating-Apps-UfPrM192vSQ
And personal favorite: https://www.discovermeteor.com/blog/updating-to-090/
I'm on osx and my mrt --version was 0.7.1 so I did a
macport selfupdate
then a
sudo port update npm
and a rehash to refresh the mrt executable (symlink to a js-file (I'm using zsh). Thank you to Matyas.
Then I did the
sudo npm update -g meteorite
mrt migrate-app
again but had a 'npm ERR! Please try running this command again as root/Administrator' which was solved with a
chown -R myUsername:staff .npm
regards
Claus
I solved it with
sudo mrt migrate-app
I don't know the possible consequences of this, use at your own risk!

Meteorite trouble with exec-sync

I've installed Meteor, Meteorite with npm.
sudo npm install -g meteor
sudo npm install -g meteorite
sudo npm install -g exec-sync
mrt create myapp
mrt add router
mrt add typescript
When I try to add a simple smart package like typescript I run into trouble. Meteorite seems download the smart package, and reports Ok, everything's ready. Here comes Meteor!. But this follows:
/home/fushunpoon/.meteorite/meteors/meteor/meteor/405cd9e86c6336bd9aaa7a8f240bb9815dceed2d/app/meteor/meteor.js:669
}).run();
^
Error: Cannot find module 'exec-sync'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:362:17)
at require (module.js:378:17)
...
(the stack trace continues).
I saw the advice on the meteor-typescript README that advises people do
sudo npm link exec-sync
but this doesn't fix the problem. Any ideas what's wrong?
EDIT: version information:
$ meteor --version
Meteor version 0.5.6 (aaa86c3e2d)
$ mrt --version
Meteorite version 0.4.7
Meteor version 0.5.6 (git checkout)
$ npm --version
1.1.62
Running on Ubuntu 12.04

Resources