lastboy / package-script Goto Github PK

Is there any options available to switch off the logging?

This is exactly what I need, however is there a way to check if packages already exist and if they do exist, don't install them?

Hi there!

do you plan to add nvm support?

2016-02-01 14:17:22.417  

************ Package Script  ************************************* process id: 31956
2016-02-01 14:17:22.444  Package Script : #node-sudo-passwd#
2016-02-01 14:22:43.345  

************ Package Script  ************************************* process id: 32665
2016-02-01 14:22:43.366  Package Script : #node-sudo-passwd#
2016-02-01 14:23:39.499  Package Script : Sorry, try again.

2016-02-01 14:23:39.501  Package Script : #node-sudo-passwd#
2016-02-01 14:27:14.790  Package Script : sudo: npm: command not found

2016-02-01 14:27:14.792  Package Script Complete 1
2016-02-01 14:27:14.804  Package Script : sudo: npm: command not found

2016-02-01 14:27:14.805  Package Script Complete 1
2016-02-01 14:27:14.815  Package Script : sudo: npm: command not found

2016-02-01 14:27:14.816  Package Script Complete 1
2016-02-01 14:27:14.828  Package Script : sudo: npm: command not found

2016-02-01 14:27:14.829  Package Script Complete 1
2016-02-01 14:27:14.842  Package Script : sudo: npm: command not found

2016-02-01 14:27:14.845  Package Script Complete 1
2016-02-01 14:27:14.846  [package-script] process completed, see pkgscript.log for more information

Hi,

how is it possible to switch off the log file?

See:
npm/npm#11279
lastboy/js.utils#1

Please do not suggest that people install packages globally at install time. This is never necessary, and is horribly brittle and just generally bad behavior.

Consider the following:

1. node_modules/.bin, ../node_modules/.bin, ../../node_modules/.bin, etc are already in the PATH when package scripts run. So, a package doesn't have to be global to be used in a script. So, globally installing deps is never required, and is unnecessary if the package (or one of its parents) has it installed locally.
2. In a typical setup, a local install is run as the normal user, and /usr/local is root-owned. Globally run package scripts are executed as the nobody user, so you are virtually guaranteed to get a EACCES or EPERM if you install something globally in a package script. This is typically not allowed, and usually won't work, unless you chown your /usr/local or do some other non-default stuff.
3. I may have a different version of grunt installed globally for a reason. If your (locally installed!) package overwrites it, that is a huge surprise! Packages should operate only within their own folders, and never outside of them.
4. Build scripts that use grunt and the like at the command line should be run at prepublish time instead of at install time. Make grunt a devDependency, and run the script on prepublish instead of install.
5. If you absolutely MUST run it at install time (and quite frankly, I've never seen a case other than binary builds with node-gyp where this is the case), then you won't be guaranteed to have your deps installed before install scripts run. In that case, list grunt (or whatever) as a bundledDependency so that you'll be guaranteed to have it from the start. You still don't need it installed globally, because the PATH is already set up to include it.

Is there a use case I'm missing that you believe requires installing things globally at your local package's install time? If so, let's address them in a different way, that doesn't rely on surprises and insecurity.