Meteor 0.9 projects fail about cli HOT 9 CLOSED

Using the patched demeteorizer to create a bundle and then issueing 'modulus deploy' does not fail, but gives errors in the log:

Can't find npm module 'uglify-js'. Did you forget to call 'Npm.depends' in package.js within the 'minifiers' package?

from cli.

@pjbrow What are the steps that you are taking to deploy your demeteorized app?

from cli.

@fiveisprime Deleted my comment. I got the process wrong.

from cli.

+1 Unable to deploy 0.9 project using modulus deploy directly (the trick of using demeteorizer 1.0 first and just deploying that dir works fine)

fs.js:438
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^
Error: EACCES, permission denied '.../project/.demeteorized/programs/server/boot.js'

from cli.

@oskarszoon how is this done? I've tried using the demeteorizer command and then modulus deploy inside the .demeteorized folder just created but I get following of error

> [email protected] install /mnt/data/1/node_modules/usage
> node-gyp rebuild

make: Entering directory `/mnt/data/1/node_modules/usage/build'
  CXX(target) Release/obj.target/sysinfo/src/binding.o
../src/binding.cpp: In function 'void RegisterModule(v8::Handle<v8::Object>)':
../src/binding.cpp:8:15: error: 'NanNew' was not declared in this scope
../src/binding.cpp:8:28: error: expected primary-expression before '>' token
../src/binding.cpp:8:53: error: expected primary-expression before '>' token
../src/binding.cpp:9:28: error: expected primary-expression before '>' token
../src/binding.cpp:9:57: error: expected primary-expression before '>' token
../src/binding.cpp:16:28: error: expected primary-expression before '>' token
../src/binding.cpp:16:50: error: expected primary-expression before '>' token
make: *** [Release/obj.target/sysinfo/src/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/nave/installed/0.10.31/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Linux 3.2.0-41-virtual
gyp ERR! command "node" "/nave/installed/0.10.31/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /mnt/data/1/node_modules/usage
gyp ERR! node -v v0.10.31
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the usage package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls usage
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.2.0-41-virtual
npm ERR! command "/mnt/nave/installed/0.10.31/bin/node" "/mnt/nave/installed/0.10.31/bin/npm" "install" "--production" "--registry" "http://registry.npmjs.org" "--cache" "/mnt/data/.npm"
npm ERR! cwd /mnt/data/1
npm ERR! node -v v0.10.31
npm ERR! npm -v 1.4.23
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /mnt/data/1/npm-debug.log
npm ERR! not ok code 0

Any news on when this package will be updated to support 0.9?

from cli.

@jakobdamjensen I was having similar issues with modulus deploy yesterday, but it appears that npm issue is resolved server side (at least for me...). I'm running a Meteor 0.9 app in Modulus right now. Using demeteorizer 1.0 (latest)

cd project
demeteorizer
cd .demeteorized
modulus deploy

from cli.

i also had the same issue, but i do not use modulus as hoster, i resolved the problem by changing
package.json file,
i added (to match the used version from meteor 0.9.x

"engines": {"node":"0.10.29"}

and changed the version of the usage package from 0.4.12 to 0.4.10

"usage": "0.4.10",

do everything works again

from cli.

The CLI has been updated to use the latest Demeteorizer as of v1.1.1 (1378342) which should resolve most issues.

Any additional issues that may pop up as a result of a failed demeteorization, please add them here and we'll get them all fixed up.

Thanks 👍

from cli.

I still get this error when i try to deploy demeteorized directory

INFO: Attaching persistent storage.
INFO: Extracting source code to application environment.
INFO: Found package.json file: /package.json
INFO: Node version not specified in package.json, using latest stable version.
INFO: Initializing Node v0.10.31
INFO: Restoring modules from previous deploy.
INFO: Running npm install.
INFO: Registry: http://registry.npmjs.org
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] punycode is also the name of a node core module.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] string_decoder is also the name of a node core module.

[email protected] install /mnt/data/2/node_modules/usage
node-gyp rebuild

make: Entering directory /mnt/data/2/node_modules/usage/build' CXX(target) Release/obj.target/sysinfo/src/binding.o ../src/binding.cpp: In function 'void RegisterModule(v8::Handle<v8::Object>)': ../src/binding.cpp:8:15: error: 'NanNew' was not declared in this scope ../src/binding.cpp:8:28: error: expected primary-expression before '>' token ../src/binding.cpp:8:53: error: expected primary-expression before '>' token ../src/binding.cpp:9:28: error: expected primary-expression before '>' token ../src/binding.cpp:9:57: error: expected primary-expression before '>' token ../src/binding.cpp:16:28: error: expected primary-expression before '>' token ../src/binding.cpp:16:50: error: expected primary-expression before '>' token make: *** [Release/obj.target/sysinfo/src/binding.o] Error 1 gyp ERR! build error make: Leaving directory/mnt/data/2/node_modules/usage/build'
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/nave/installed/0.10.31/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Linux 3.13.0-35-generic
gyp ERR! command "node" "/nave/installed/0.10.31/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /mnt/data/2/node_modules/usage
gyp ERR! node -v v0.10.31
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the usage package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls usage
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.13.0-35-generic
npm ERR! command "/mnt/nave/installed/0.10.31/bin/node" "/mnt/nave/installed/0.10.31/bin/npm" "install" "--production" "--registry" "http://registry.npmjs.org" "--cache" "/mnt/data/.npm"
npm ERR! cwd /mnt/data/2
npm ERR! node -v v0.10.31
npm ERR! npm -v 1.4.23
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /mnt/data/2/npm-debug.log
npm ERR! not ok code 0
INFO: Main file specified in package.json: main.js
INFO: Starting application.

[✓] Nanuism Admin running at nanuism-admin-22164.onmodulus.net
mile:.demeteorized mile$ npm update node-gyp
mile:.demeteorized mile$ npm update node-gyp
mile:.demeteorized mile$ npm install
npm WARN package.json [email protected] No repository field.
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"0.10.31","npm":"1.4.23"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"0.10.31","npm":"1.4.23"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"0.10.31","npm":"1.4.23"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"0.10.31","npm":"1.4.23"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"0.10.31","npm":"1.4.23"})

[email protected] install /Users/mile/Sites/nanuism/.demeteorized/node_modules/bcrypt
node-gyp rebuild

CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
SOLINK_MODULE(target) Release/bcrypt_lib.node
SOLINK_MODULE(target) Release/bcrypt_lib.node: Finished

[email protected] install /Users/mile/Sites/nanuism/.demeteorized/node_modules/usage
node-gyp rebuild

CXX(target) Release/obj.target/sysinfo/src/binding.o
../src/binding.cpp:16:15: error: use of undeclared identifier 'NanNew'
target->Set(NanNew("OS"), NanNew(OS));
^
../src/binding.cpp:16:22: error: 'String' does not refer to a value
target->Set(NanNew("OS"), NanNew(OS));
^
/Users/mile/.node-gyp/0.10.31/deps/v8/include/v8.h:1024:7: note: declared here
class String : public Primitive {
^
2 errors generated.
make: *** [Release/obj.target/sysinfo/src/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Darwin 13.3.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/mile/Sites/nanuism/.demeteorized/node_modules/usage
gyp ERR! node -v v0.10.31
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok

[email protected] install /Users/mile/Sites/nanuism/.demeteorized/node_modules/fibers
node ./build.js

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/fibers.node
SOLINK_MODULE(target) Release/fibers.node: Finished
Installed in /Users/mile/Sites/nanuism/.demeteorized/node_modules/fibers/bin/darwin-x64-v8-3.14/fibers.node
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the usage package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls usage
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 13.3.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/mile/Sites/nanuism/.demeteorized
npm ERR! node -v v0.10.31
npm ERR! npm -v 1.4.23
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/mile/Sites/nanuism/.demeteorized/npm-debug.log
npm ERR! not ok code 0

from cli.