linnovate / mean-cli Goto Github PK

meanio cli npm package

License: MIT License

JavaScript 94.77% CSS 0.07% HTML 1.80% Shell 3.36%

mean-cli's Introduction

MEAN Command Line

Source for npm package meanio. mean-cli is a core package of the mean.io project and is used primarily to manage packages for extending functionality, for example adding a package to enable inline editable tokens.

The cli provides a lot of useful functionality, such as scaffolding options to create new packages, assign roles to users, check the mongo status, add/remove packages and list currently installed packages.

See http://mean.io/#!/docs for more in-depth information about mean.

The repository contains

The bin file used for cli operations.
Core functionality for managing mean packages.

Basic Usage

Install Package:

$ [sudo] npm install -g mean-cli

Note: You may need to use sudo only for OSX, *nix, BSD etc and run your command shell as Administrator (for Windows)

Explore CLI functionality:

$ mean --help

Create a new mean app:

$ mean init <NameOfYourApp>

Install Dependencies:

$ cd <NameOfYourApp> && npm install

Create a sample mean package:

$ mean package <NameOfYourPackage>

Run your app:

$ gulp

mean-cli's People

Contributors

Stargazers

Watchers

Forkers

mchapman andrewwong1221 fredl sohailalam2 cremafr kbeyer elementstorm mkelley33 yourdeveloper bluemir jafernandez73 rangken tekton udisun hyperiancorporation jamotion thomastaylor312 ahmadel-banna oripekelman andrija-hers tkh44 veljkopopovic movibe lirantal ntadic sybarite silverbux raphaelfeng emps fracmak almogbaku iolufemi dizaina dgtery michaelwills brownman jeff-lewis peterblazejewicz djskinner aldoritma jtetrault laurencedablo woganmay daball samirbr sibustephen steezeburger jwebbdev clowenhg strudi ralic vikramtiwari bransbury nox-404 autodesk-forks bannerchi rui-hai dexter0201 miqueliniesta jamesnik rogeriob2br dawidpolakowski crazyrex voidp34r

mean-cli's Issues

Mean Install should support specific branch/tags/commit id for a package?

I want to test the preinstall script of comments, and am confused on how to indicate to the mean install script to install a particular release of the project?

I tried this mean install comments#vp6 but it made no difference.

Can we please build support for this?

suggestion: README: +gitter

suggestion:

update README.md with a link to gitter on top

package.json mangled after mean init

Problem: After mean init <project> completes, <project>/package.json is malformed. Exact problems with the file vary, but tend to be the last few characters of the file repeated. For example:

$ tail project/package.json 
    "gulp-rimraf": "^0.1.1",
    "gulp-uglify": "^1.0.1",
    "gulp-util": "^3.0.1",
    "jshint-stylish": "^1.0.0",
    "through": "^2.3.6"
  }
}
6"
  }
}

I suspect a race condition, I don't have a patch yet, but here are some of my findings so far:

https://github.com/linnovate/mean-cli/blob/master/lib/cli.js#L920

jsonFile() on that line returns a promise, so execution continues down to this write:

https://github.com/linnovate/mean-cli/blob/master/lib/cli.js#L953

In fact, if I sprinkle some console.log calls in there, the write on line 953 executes before the one on line 927. This confirms the race theory.

For reference, this is the relevant jsonFile() source (pkg json-file-plus):

https://github.com/ljharb/node-json-file/blob/master/index.js#L46

command: mean list

needed option:
--remote: for listing remote packages

mean skeleton: is test-ready ?

mean skeletom app should be test ready:

├── custom
--- here we need to duplicate the structure to: {src/  , test/}
│   ├── MY_COOL_PACKAGE
│   │   ├── public
│   │   │   ├── assets
│   │   │   ├── controllers
│   │   │   ├── routes
│   │   │   ├── services
│   │   │   └── views
│   │   └── server
│   │       ├── controllers
│   │       ├── routes
│   │       └── views

Better error reporting. (Prompted by `mean register` and `mean init`)

Several different issues that have surfaced recently have had little to no evidence initially of their root cause including mean register username length and mean init package installation (differences between bower dependencies on install and postinstall). Unfortunately the actual cause for mean init errors for installing packages with postinstall is still unknown, and if a user were to try to create a username over 15 characters, it wouldn't give them a very informative message.

some package will not be loaded!

function searchSource(source, callback) {
        fs.readdir(path.join(process.cwd(), source), function(err, files) {
            if (err || !files || !files.length) {
                if (err && err.code !== 'ENOENT') console.log(err);
                return callback();
            }
            files.forEach(function(file, index) {
                fs.readFile(path.join(process.cwd(), source, file, 'package.json'), function(fileErr, data) {
                    if (data) {
                        try {
                            var json = JSON.parse(data.toString());
                            if (json.mean) {
                                modules[file] = {
                                    version: json.version,
                                    source: source
                                };
                            }
                        } catch (err) {
                            return callback();
                        }
                    }
                    if (files.length - 1 === index) return callback(); 
                });
            });
        });
    }

here: if (files.length - 1 === index) return callback();
you can not make it sure that the last index file will be loaded at the end!

this issue will make some package be loaded incomplete!

sorry for my english!

Add .bower.json to packge scaffolding

Fill in attributes basedon the stuff going in to package.json (name, version etc..)

download and add remote finstead of cloning

This is correct both for the mean repo installed in mean init and for the packages installed.
Provide benchmarks of before and after to understand how much faster it runs

Cannot installl mean packages behind proxy server

when installing mean packages using command
mean install mean-admin
returns
Package not found

it is working with normal connections

i think while cloning the package
it clones from
git clone git://linnovate/mean-admin something like this

changing it to
git clone https://github.com/linnvate/mean will solve the problem

please help

Git check

A couple users have reported errors when running mean init because git is not installed. See linnovate/mean#372.

We should add a check to ensure git is available prior to running the clone command, and display an obvious error if not. Potentially, there should also be a similar check for npm.

installation problems windows 8.1

Command line listing:

c:>npm install -g mean-cli
npm WARN engine [email protected]: wanted: {"node":"0.10.x","npm":"2.1.x"} (current
: {"node":"0.10.32","npm":"1.4.28"})

[email protected] preinstall C:\Users\Taras\AppData\Roaming\npm\node_modules\mean
-cli
node ./scripts/preinstall

events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1001:11)
at Process.ChildProcess._handle.onexit (child_process.js:792:34)

npm ERR! [email protected] preinstall: node ./scripts/preinstall
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is most likely a problem with the mean-cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./scripts/preinstall
npm ERR! You can get their info via:
npm ERR! npm owner ls mean-cli
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "mean-cli"
npm ERR! cwd c:
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

mean uninstall doesn't work

Mean uninstall does not seem to work.
I seem it's because of the changes of the contrib/custom directories.

UI: mean-init myApp

do u really want to call this app myApp ?
user can press control+c - no need to re-edit this field.

Enable aggregation from remote url

Curently aggregateAsset works only with local files if we add a paramater (like the current js/css) called url we will get and aggregate that asset in as well.

Provide a more descriptive error upon executing as sudo/root when bower fails.

A simple error message that explains that it must be run without sudo/root will be less confusing for new users.

Ask about `mean-admin` in install wizard

Instead of always installing mean-admin, we should prompt the user. Default to yes.

mean status

should indicate which NODE_ENV is being used
validate configuration of all 3 env: test/dev/prod

Mongo/mongoose Installation detection and prompt

Instead of assuming Mongo and Mongoose are present, prompt to install or print error and halt.

aggregated.js - files end up as one line each.

In aggregated.js files are concatenated one per line.
This makes debugging of client side code very hard.

I propose to use simple concatenation in development mode (without removing white spaces and new lines).

Mean Install should support tags, branches, commit id

This is necessary for package development process.

I can't find the original issue, so had to recreate it.

mean docs should open learn.mean.io

the (cute ) mean docs command should open learn.mean.io

Prompt users to confirm they want to init/install as root.

A prompt to inform the user they may not want to install as root would help them avoid some currently obscure errors.

When I init mean use "mean init myApp",failed and it shows this error

C:\Users\yanggaofei\AppData\Roaming\npm\node_modules\mean-cli\node_modules\inqui
rer\node_modules\rx\dist\rx.all.js:9229
throw e;
^
ReferenceError: parent is not defined
at AnonymousObserver._onNext (C:\Users\yanggaofei\AppData\Roaming\npm\node_m
odules\mean-cli\node_modules\inquirer\node_modules\rx\dist\rx.all.js:4259:63)
at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (C:\Users\y
anggaofei\AppData\Roaming\npm\node_modules\mean-cli\node_modules\inquirer\node_m
odules\rx\dist\rx.all.js:1863:12)
at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (
C:\Users\yanggaofei\AppData\Roaming\npm\node_modules\mean-cli\node_modules\inqui
rer\node_modules\rx\dist\rx.all.js:1795:35)
....

Installation error on `ubuntu aptitude npm`

almog@chiefangel:~$ sudo npm install -g mean-cli
npm WARN engine [email protected]: wanted: {"node":"0.10.x","npm":"2.1.x"} (current: {"node":"0.10.25","npm":"1.4.21"})

> [email protected] preinstall /usr/local/lib/node_modules/mean-cli
> node ./scripts/preinstall

sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! [email protected] preinstall: `node ./scripts/preinstall`
npm ERR! Exit status 127
npm ERR! 
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is most likely a problem with the mean-cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./scripts/preinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls mean-cli
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.16.0-23-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "mean-cli"
npm ERR! cwd /home/almog
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/almog/npm-debug.log
npm ERR! not ok code 0

I guess it happened because in ubuntu node installed as nodejs and not as node

Add .bowerrc to package scaffolding

Currently this is a manual step but if we want to enforce policy and install the bower dependencies in public/assets/lib instead of bower_components it needs to be part of the scaffolding.
See this for reference (2.4) - http://blog.mean.io/2014/08/build-a-package-gmap/

mean-init: check for latest available version of mean-cli

check for latest version before continue to actual scaffolding

Cant register with 'mean register'

I am unable to publish any mean packages as I cant register myself with mean. I get an error saying 'registration failed' when I try to register through terminal.

mean install/uninstall should add/remove package dependency from mean.json

via @AlmogBaku.
Make sure that mean install package adds a dependency in the mean.json
and that mean uninstalls removes.

prompt: mean.logo.ascii-art

proposal:

paint it red when installation fails

inquirer vs prompt

The inquirer and prompt modules do basically the same thing, and both are implemented by this project. We should refactor to use only one- my strong preference is with inquirer.

mean search

result should indicate the status of the package: public/private

mean-init: user interaction should be easier

mean-init should not restrict the user from using both: gulp & grunt

options:

set defaults to use both
else?

OPTION: add

required option: Add

it should be easy to update mean.json using just:
mean-cli add

mean list should list every package installed

I have packages installed (the default set) which don't show up in mean list:

$ mean list
   MEAN Packages List:
   -----------------
   No core Packages
   No custom Packages
   contrib: [email protected]  Author: Linnovate
$ ls packages
access  articles  contrib  system  theme  users

mean install x1 x2

required:
support for installing multiple packages using:
$ mean install

"mean preinstall" is not implemented?

I tried "mean preinstall" to install contrib package but I got:

proudside-lm:DigitEduPrototype hepengzhang$ mean preinstall

  cli.preinstall();
  ^
  TypeError: Object #<Object> has no method 'preinstall'
  at Object.<anonymous> (/usr/local/lib/node_modules/mean-cli/bin/mean-preinstall:12:5)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Function.Module.runMain (module.js:497:10)
  at startup (node.js:119:16)
  at node.js:906:3

It seems "preinstall" is not implemented yet, right?

Don't assume shell.exec() is synchronous

While investigating #94 I noticed that in some places there is an assumption that shell.exec() is synchronous. In fact, it is not when a callback is provided:

https://github.com/arturadib/shelljs#execcommand--options--callback

In this case, for example, init() will return immediately since shell.exec() is the last statement in the function. It's not clear whether init() is expected to fully complete its work before returning:

https://github.com/linnovate/mean-cli/blob/master/lib/cli.js#L896

I've no evidence this is a problem right now, but if the caller does expect init to be finished upon returning, then script could conceivably exit before the callback has a chance to run. Either init() should explicitly return a promise, take a callback, or ensure it completes its work before returning.

In this case, assuming we want the latter, simply adding {async:false} should do the trick.

mean is broken because of an inquiry dependency (mx)

This commit fixes it.
liorkesos/Inquirer.js@91b1fe2
We either wait for inquirer to fix or we fork inquirer and temporary release it to bridge the time mean.io is broken.

mean init: doesn't find 'git'

root@850a7ee94c4b:~# mean-init 
? What would you name your mean app? mean
? Do you prefer grunt or gulp as a taskrunner? grunt
    Prerequisite not installed: git
root@850a7ee94c4b:~# which git
/usr/bin/git
root@850a7ee94c4b:~# echo $PATH | grep '/usr/bin'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin
root@850a7ee94c4b:~# mean -v
0.9.8
root@850a7ee94c4b:~#

package maintenance.

/it may be a good tip for presenting the user the option to replace:
version number: '--latest'
to the latest stable release.

the default user's answer shoud be yes (Y/n).

Mean package should create CRUD routes and functions rather than current routes

Kinda like rails when we do scaffolding and generate the basic routes, instead of the current content created. It would be much better if mean package creates basic services on angular end with forms and crud functions are created on the node end. Exactly like articles in fact! Schemas can just include a title initially....In fact, we want to emphasize on test cases and TDD. So instead of blank folders, basic test suite should be created as well for that package with tests which pass.

Having developed on mean.io for the last year and so, this is what most of our packages initially constitute before it gets trickier. So I definitely see that as a better starting point.

Thoughts - Feel free to chime in, or give me a thumbs up, if you'd like this feature.

Binary pollution under /usr/local/bin

The way we deploy today places 17 binaries under /usr/local/bin - as seen in the picture we have "neighbours" like meteor, hapi, docker or spark that have similar clis and deliver them with a single binary.
Although no one has complained (yet) I think the best practice would be to use a single binary and move the "diversity" under lib.

mean publish should present help text + prompt for confirmation

Text containing the process and flow (+ link to learn more)
Prompt to confirm and publish only on the yes.

Fix packages installed with mean init prompt.

This needs to be inspected more closely. mean-admin seems to install and work fine, but other packages (tokens and upload) fail with bower related errors. This is probably due to their package related json files. It may also be due to a fundamental difference in how install and postinstall work, since the same packages install (also producing vague bower related warnings) and work when installed from mean install.

mean-cli install fail :(

Hi @zohar @zlokomatic @bjornkri @OriPekelman @AlmogBaku @brownman

Can you help me!!

npm WARN engine [email protected]: wanted: {"node":"0.10.x","npm":"2.1.x"} (current: {"node":"0.10.33","npm":"2.6.0"})

[email protected] preinstall /root/.nvm/v0.10.33/lib/node_modules/mean-cli
node ./scripts/preinstall

sh: node: command not found
npm ERR! Linux 3.2.0-4-amd64
npm ERR! argv "node" "/root/.nvm/v0.10.33/bin/npm" "install" "-g" "mean-cli"
npm ERR! node v0.10.33
npm ERR! npm v2.6.0
npm ERR! code ELIFECYCLE

npm ERR! [email protected] preinstall: node ./scripts/preinstall
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the [email protected] preinstall script 'node ./scripts/preinstall'.
npm ERR! This is most likely a problem with the mean-cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./scripts/preinstall
npm ERR! You can get their info via:
npm ERR! npm owner ls mean-cli
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /share/project/npm-debug.log

mean search

required:
more details about the package.

mean search translate returns 2 results:
which one is better ?

[SUGGESTION] Install cli locally

Would'nt it be a good idea to have a global package as small as possible like grunt-cli, which will load the locally installed mean-console (for example)?

It would be easier to have some package to register some commands, to have a console tool a bit like symfony.

'mean install PACKAGE' doesn't register anything in the repo

Is there no 'mean.json' file anywhere, or a way to register vendor packages in package.json? It would be useful for working across multiple environments, so you could run

mean install

the same way as you would with npm. Running

npm install mean-admin

returns an npm complaint that it can't find the package.

mean install mean-admin --save

does not modify anything.

$ mean install --save mean-admin
error: unknown option `--save'
$

The only way around this I can think of is to add an update script to grunt to run those installs.

mean-cli install failure on Mac OS X Yosemite

Fell at the first. Any idea what's happening here?

Many thanks
Al

Alans-MBP:~ amcginlay$ sudo npm install -g mean-cli
Password:
|

[email protected] preinstall /usr/local/lib/node_modules/mean-cli
node ./scripts/preinstall

shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied

node.js:815
var cwd = process.cwd();
^
Error: EACCES, permission denied
at Function.startup.resolveArgv0 (node.js:815:23)
at startup (node.js:58:13)
at node.js:906:3
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "mean-cli"
npm ERR! node v0.10.32
npm ERR! npm v2.1.5
npm ERR! code ELIFECYCLE

npm ERR! Please include the following file with any support request:
npm ERR! /Users/amcginlay/npm-debug.log
Alans-MBP:~ amcginlay$

------------------------------------------ /Users/amcginlay/npm-debug.log --------------------------------------
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'install', '-g', 'mean-cli' ]
2 info using [email protected]
3 info using [email protected]
4 verbose node symlink /usr/local/bin/node
5 silly cache add args [ 'mean-cli', null ]
6 verbose cache add spec mean-cli
7 silly cache add parsed spec { raw: 'mean-cli',
7 silly cache add scope: null,
7 silly cache add name: 'mean-cli',
7 silly cache add rawSpec: '',
7 silly cache add spec: '',
7 silly cache add type: 'range' }
8 verbose addNamed mean-cli@
9 silly addNamed semver.valid null
10 silly addNamed semver.validRange *
11 silly addNameRange { name: 'mean-cli', range: '', hasData: false }
12 verbose mapToRegistry name mean-cli
13 verbose mapToRegistry uri https://registry.npmjs.org/mean-cli
14 verbose addNameRange registry:https://registry.npmjs.org/mean-cli not in flight; fetching
15 verbose request on initialization, where is /mean-cli
16 verbose request after pass 1, where is /mean-cli
17 verbose request url raw /mean-cli
18 verbose request resolving registry [ 'https://registry.npmjs.org/', './mean-cli' ]
19 verbose request after pass 2, where is https://registry.npmjs.org/mean-cli
20 verbose request no auth needed
21 info attempt registry request try #1 at 21:24:16
22 verbose request id eab5194252752344
23 verbose etag "7MN8T1W57I4XJQLHHKR5D5166"
24 http request GET https://registry.npmjs.org/mean-cli
25 http 304 https://registry.npmjs.org/mean-cli
26 silly registry.get cb [ 304,
26 silly registry.get { date: 'Sat, 25 Oct 2014 20:24:16 GMT',
26 silly registry.get server: 'Apache',
26 silly registry.get via: '1.1 varnish',
26 silly registry.get 'last-modified': 'Sat, 25 Oct 2014 20:24:16 GMT',
26 silly registry.get 'cache-control': 'max-age=60',
26 silly registry.get etag: '"7MN8T1W57I4XJQLHHKR5D5166"',
26 silly registry.get age: '0',
26 silly registry.get 'x-served-by': 'cache-lhr6334-LHR',
26 silly registry.get 'x-cache': 'MISS',
26 silly registry.get 'x-cache-hits': '0',
26 silly registry.get 'x-timer': 'S1414268656.021400,VS0,VE89',
26 silly registry.get vary: 'Accept',
26 silly registry.get 'content-length': '0',
26 silly registry.get 'keep-alive': 'timeout=10, max=50',
26 silly registry.get connection: 'Keep-Alive' } ]
27 verbose etag https://registry.npmjs.org/mean-cli from cache
28 silly addNameRange number 2 { name: 'mean-cli', range: '', hasData: true }
29 silly addNameRange versions [ 'mean-cli',
29 silly addNameRange [ '0.0.0',
29 silly addNameRange '0.0.1',
29 silly addNameRange '0.0.2',
29 silly addNameRange '0.0.3',
29 silly addNameRange '0.0.4',
29 silly addNameRange '0.5.25',
29 silly addNameRange '0.5.26',
29 silly addNameRange '0.5.27',
29 silly addNameRange '0.5.31',
29 silly addNameRange '0.5.34',
29 silly addNameRange '0.9.0',
29 silly addNameRange '0.9.1',
29 silly addNameRange '0.0.9',
29 silly addNameRange '0.0.10',
29 silly addNameRange '0.0.11',
29 silly addNameRange '0.0.12',
29 silly addNameRange '0.9.2',
29 silly addNameRange '0.9.3' ] ]
30 verbose addNamed [email protected]
31 silly addNamed semver.valid 0.9.3
32 silly addNamed semver.validRange 0.9.3
33 silly cache afterAdd [email protected]
34 verbose afterAdd /Users/amcginlay/.npm/mean-cli/0.9.3/package/package.json not in flight; writing
35 verbose afterAdd /Users/amcginlay/.npm/mean-cli/0.9.3/package/package.json written
36 silly install resolved [ { name: 'mean-cli',
36 silly install resolved version: '0.9.3',
36 silly install resolved preferGlobal: true,
36 silly install resolved description: 'Simple command line interface for installing and managing MEAN apps',
36 silly install resolved author: { name: 'linnovate' },
36 silly install resolved contributors: [ [Object], [Object], [Object], [Object] ],
36 silly install resolved license: 'AGPL',
36 silly install resolved main: 'index',
36 silly install resolved scripts: { preinstall: 'node ./scripts/preinstall' },
36 silly install resolved bin:
36 silly install resolved { mean: './bin/mean',
36 silly install resolved 'mean-init': './bin/mean-init',
36 silly install resolved 'mean-authorize': './bin/mean-authorize',
36 silly install resolved 'mean-whoami': './bin/mean-whoami',
36 silly install resolved 'mean-login': './bin/mean-login',
36 silly install resolved 'mean-addKey': './bin/mean-addKey',
36 silly install resolved 'mean-publish': './bin/mean-publish',
36 silly install resolved 'mean-search': './bin/mean-search',
36 silly install resolved 'mean-register': './bin/mean-register',
36 silly install resolved 'mean-postinstall': './bin/mean-postinstall',
36 silly install resolved 'mean-preinstall': './bin/mean-preinstall',
36 silly install resolved 'mean-install': './bin/mean-install',
36 silly install resolved 'mean-uninstall': './bin/mean-uninstall',
36 silly install resolved 'mean-docs': './bin/mean-docs',
36 silly install resolved 'mean-package': './bin/mean-package',
36 silly install resolved 'mean-list': './bin/mean-list',
36 silly install resolved 'mean-status': './bin/mean-status',
36 silly install resolved 'mean-user': './bin/mean-user' },
36 silly install resolved repository:
36 silly install resolved { type: 'git',
36 silly install resolved url: 'https://github.com/linnovate/mean-cli.git' },
36 silly install resolved keywords: [ 'mean', 'meanio', 'mean.io', 'mean-cli' ],
36 silly install resolved engines: { node: '0.10.x', npm: '2.1.x' },
36 silly install resolved dependencies:
36 silly install resolved { bower: '^1.3.8',
36 silly install resolved chalk: '^0.5.1',
36 silly install resolved commander: '^2.4.0',
36 silly install resolved lodash: '^2.4.1',
36 silly install resolved 'mean-health': '~0.1.3',
36 silly install resolved mongoose: '^3.8.12',
36 silly install resolved npm: '^2.1.0',
36 silly install resolved opener: '^1.3.0',
36 silly install resolved prompt: '^0.2.13',
36 silly install resolved request: 'latest',
36 silly install resolved shelljs: '^0.3.0' },
36 silly install resolved devDependencies:
36 silly install resolved { grunt: '^0.4.4',
36 silly install resolved 'grunt-contrib-jshint': '^0.10.0',
36 silly install resolved 'grunt-mocha-test': '^0.10.0',
36 silly install resolved mocha: '^1.18.2',
36 silly install resolved should: '^3.2.0' },
36 silly install resolved gitHead: '6e3ac3805a39385a16b8b1df20a02a535f555c0d',
36 silly install resolved bugs: { url: 'https://github.com/linnovate/mean-cli/issues' },
36 silly install resolved homepage: 'https://github.com/linnovate/mean-cli',
36 silly install resolved _id: '[email protected]',
36 silly install resolved _shasum: '96bc2357adb0e0d113c0fa52529d23dc0d19e159',
36 silly install resolved _from: 'mean-cli@*',
36 silly install resolved _npmVersion: '2.1.4',
36 silly install resolved _nodeVersion: '0.10.32',
36 silly install resolved _npmUser: { name: 'fyockm', email: '[email protected]' },
36 silly install resolved maintainers: [ [Object], [Object], [Object] ],
36 silly install resolved dist:
36 silly install resolved { shasum: '96bc2357adb0e0d113c0fa52529d23dc0d19e159',
36 silly install resolved tarball: 'http://registry.npmjs.org/mean-cli/-/mean-cli-0.9.3.tgz' },
36 silly install resolved directories: {},
36 silly install resolved _resolved: 'https://registry.npmjs.org/mean-cli/-/mean-cli-0.9.3.tgz',
36 silly install resolved readme: 'ERROR: No README data found!' } ]
37 info install [email protected] into /usr/local/lib
38 info installOne [email protected]
39 verbose installOne of mean-cli to /usr/local/lib not in flight; installing
40 verbose lock using /Users/amcginlay/.npm/_locks/mean-cli-66865dbd2b085805.lock for /usr/local/lib/node_modules/mean-cli
41 silly install write writing mean-cli 0.9.3 to /usr/local/lib/node_modules/mean-cli
42 silly cache addNamed cb [email protected]
43 verbose unbuild lib/node_modules/mean-cli
44 verbose gentlyRm vacuuming /usr/local/lib/node_modules/mean-cli
45 verbose tar unpack /Users/amcginlay/.npm/mean-cli/0.9.3/package.tgz
46 verbose tar unpacking to /usr/local/lib/node_modules/mean-cli
47 verbose gentlyRm vacuuming /usr/local/lib/node_modules/mean-cli
48 silly gunzTarPerm modes [ '755', '644' ]
49 silly gunzTarPerm extractEntry package.json
50 silly gunzTarPerm extractEntry .npmignore
51 silly gunzTarPerm extractEntry README.md
52 silly gunzTarPerm extractEntry LICENSE
53 silly gunzTarPerm extractEntry Gruntfile.js
54 silly gunzTarPerm extractEntry index.js
55 silly gunzTarPerm extractEntry bin/mean-package
56 silly gunzTarPerm extractEntry bin/mean
57 silly gunzTarPerm extractEntry bin/mean-authorize
58 silly gunzTarPerm extractEntry bin/mean-docs
59 silly gunzTarPerm extractEntry bin/mean-init
60 silly gunzTarPerm extractEntry bin/mean-install
61 silly gunzTarPerm extractEntry bin/mean-list
62 silly gunzTarPerm extractEntry bin/mean-login
63 silly gunzTarPerm extractEntry bin/mean-logout
64 silly gunzTarPerm extractEntry bin/mean-addKey
65 silly gunzTarPerm extractEntry bin/mean-postinstall
66 silly gunzTarPerm extractEntry bin/mean-preinstall
67 silly gunzTarPerm extractEntry bin/mean-publish
68 silly gunzTarPerm extractEntry bin/mean-register
69 silly gunzTarPerm extractEntry bin/mean-search
70 silly gunzTarPerm extractEntry bin/mean-status
71 silly gunzTarPerm extractEntry bin/mean-uninstall
72 silly gunzTarPerm extractEntry bin/mean-user
73 silly gunzTarPerm extractEntry bin/mean-whoami
74 silly gunzTarPerm extractEntry CONTRIBUTING.md
75 silly gunzTarPerm extractEntry img/logo.txt
76 silly gunzTarPerm extractEntry img/meanlogo.png
77 silly gunzTarPerm extractEntry lib/cli.js
78 silly gunzTarPerm extractEntry lib/scaffold.js
79 silly gunzTarPerm extractEntry lib/templates/package.json
80 silly gunzTarPerm extractEntry lib/templates/app.js
81 silly gunzTarPerm extractEntry lib/templates/.bowerrc
82 silly gunzTarPerm extractEntry lib/templates/assets.css
83 silly gunzTarPerm extractEntry lib/templates/bower.json
84 silly gunzTarPerm extractEntry lib/templates/client/controller.js
85 silly gunzTarPerm extractEntry lib/templates/client/package.js
86 silly gunzTarPerm extractEntry lib/templates/client/routes.js
87 silly gunzTarPerm extractEntry lib/templates/client/service.js
88 silly gunzTarPerm extractEntry lib/templates/client/view.html
89 silly gunzTarPerm extractEntry lib/templates/server/routes.js
90 silly gunzTarPerm extractEntry lib/templates/server/view.html
91 silly gunzTarPerm extractEntry scripts/preinstall.js
92 silly gunzTarPerm extractEntry .jshintrc
93 silly gunzTarPerm extractEntry test/bin/mean_test.js
94 info preinstall [email protected]
95 verbose unsafe-perm in lifecycle false
96 info [email protected] Failed to exec preinstall script
97 verbose unlock done using /Users/amcginlay/.npm/_locks/mean-cli-66865dbd2b085805.lock for /usr/local/lib/node_modules/mean-cli
98 verbose stack Error: [email protected] preinstall: node ./scripts/preinstall
98 verbose stack Exit status 8
98 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:212:16)
98 verbose stack at ChildProcess.emit (events.js:98:17)
98 verbose stack at maybeClose (child_process.js:756:16)
98 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:823:5)
99 verbose pkgid [email protected]
100 verbose cwd /Users/amcginlay
101 error Darwin 14.0.0
102 error argv "node" "/usr/local/bin/npm" "install" "-g" "mean-cli"
103 error node v0.10.32
104 error npm v2.1.5
105 error code ELIFECYCLE
106 error [email protected] preinstall: node ./scripts/preinstall
106 error Exit status 8
107 error Failed at the [email protected] preinstall script.
107 error This is most likely a problem with the mean-cli package,
107 error not with npm itself.
107 error Tell the author that this fails on your system:
107 error node ./scripts/preinstall
107 error You can get their info via:
107 error npm owner ls mean-cli
107 error There is likely additional logging output above.
108 verbose exit [ 1, true ]
109 verbose unbuild lib/node_modules/mean-cli
110 info preuninstall [email protected]
111 info uninstall [email protected]
112 verbose unbuild rmStuff [email protected] from /usr/local/lib/node_modules
113 verbose /usr/local/bin,[object Object] binRoot
114 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
115 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
116 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
117 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
118 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
119 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
120 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
121 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
122 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
123 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
124 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
125 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
126 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
127 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
128 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
129 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
130 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
131 verbose gentlyRm verifying that /usr/local/lib/node_modules/mean-cli is managed by npm
132 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
133 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
134 silly gentlyRm /usr/local/bin/mean is not under /usr/local/lib/node_modules/mean-cli
135 silly gentlyRm checking to see if /usr/local/bin/mean is a link
136 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
137 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
138 silly gentlyRm /usr/local/bin/mean-init is not under /usr/local/lib/node_modules/mean-cli
139 silly gentlyRm checking to see if /usr/local/bin/mean-init is a link
140 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
141 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
142 silly gentlyRm /usr/local/bin/mean-authorize is not under /usr/local/lib/node_modules/mean-cli
143 silly gentlyRm checking to see if /usr/local/bin/mean-authorize is a link
144 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
145 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
146 silly gentlyRm /usr/local/bin/mean-whoami is not under /usr/local/lib/node_modules/mean-cli
147 silly gentlyRm checking to see if /usr/local/bin/mean-whoami is a link
148 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
149 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
150 silly gentlyRm /usr/local/bin/mean-login is not under /usr/local/lib/node_modules/mean-cli
151 silly gentlyRm checking to see if /usr/local/bin/mean-login is a link
152 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
153 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
154 silly gentlyRm /usr/local/bin/mean-addKey is not under /usr/local/lib/node_modules/mean-cli
155 silly gentlyRm checking to see if /usr/local/bin/mean-addKey is a link
156 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
157 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
158 silly gentlyRm /usr/local/bin/mean-publish is not under /usr/local/lib/node_modules/mean-cli
159 silly gentlyRm checking to see if /usr/local/bin/mean-publish is a link
160 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
161 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
162 silly gentlyRm /usr/local/bin/mean-search is not under /usr/local/lib/node_modules/mean-cli
163 silly gentlyRm checking to see if /usr/local/bin/mean-search is a link
164 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
165 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
166 silly gentlyRm /usr/local/bin/mean-register is not under /usr/local/lib/node_modules/mean-cli
167 silly gentlyRm checking to see if /usr/local/bin/mean-register is a link
168 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
169 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
170 silly gentlyRm /usr/local/bin/mean-postinstall is not under /usr/local/lib/node_modules/mean-cli
171 silly gentlyRm checking to see if /usr/local/bin/mean-postinstall is a link
172 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
173 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
174 silly gentlyRm /usr/local/bin/mean-preinstall is not under /usr/local/lib/node_modules/mean-cli
175 silly gentlyRm checking to see if /usr/local/bin/mean-preinstall is a link
176 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
177 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
178 silly gentlyRm /usr/local/bin/mean-install is not under /usr/local/lib/node_modules/mean-cli
179 silly gentlyRm checking to see if /usr/local/bin/mean-install is a link
180 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
181 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
182 silly gentlyRm /usr/local/bin/mean-uninstall is not under /usr/local/lib/node_modules/mean-cli
183 silly gentlyRm checking to see if /usr/local/bin/mean-uninstall is a link
184 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
185 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
186 silly gentlyRm /usr/local/bin/mean-docs is not under /usr/local/lib/node_modules/mean-cli
187 silly gentlyRm checking to see if /usr/local/bin/mean-docs is a link
188 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
189 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
190 silly gentlyRm /usr/local/bin/mean-package is not under /usr/local/lib/node_modules/mean-cli
191 silly gentlyRm checking to see if /usr/local/bin/mean-package is a link
192 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
193 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
194 silly gentlyRm /usr/local/bin/mean-list is not under /usr/local/lib/node_modules/mean-cli
195 silly gentlyRm checking to see if /usr/local/bin/mean-list is a link
196 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
197 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
198 silly gentlyRm /usr/local/bin/mean-status is not under /usr/local/lib/node_modules/mean-cli
199 silly gentlyRm checking to see if /usr/local/bin/mean-status is a link
200 silly cacheAndTest /usr/local/lib/node_modules/mean-cli is inside /usr/local/lib/node_modules
201 silly gentlyRm /usr/local/lib/node_modules/mean-cli is managed by npm
202 silly gentlyRm /usr/local/bin/mean-user is not under /usr/local/lib/node_modules/mean-cli
203 silly gentlyRm checking to see if /usr/local/bin/mean-user is a link
204 info postuninstall [email protected]
205 verbose gentlyRm vacuuming /usr/local/lib/node_modules/mean-cli
206 silly gentlyRm purging /usr/local/lib/node_modules/mean-cli
207 silly gentlyRm quitting because other entries in /usr/local/lib/node_modules

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.