I have a Windows 7 / 64bit machine and currenlty trying to deploy node.js based project to nodejitsu. But it do not works as expected and crash with error:
Executing command deploy
info: Welcome to Nodejitsu yourapp
info: jitsu v0.13.15, node v0.11.10
info: It worked if it ends with Nodejitsu ok
warn: You are using unstable version of node.js. You may experience problems.
info: Executing command deploy
c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\lib\jitsu\package.js:248
jitsu.log.warn(line);
^
TypeError: Cannot call method 'warn' of undefined
at c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\lib\jitsu\package.js:248:17
at Array.forEach (native)
at c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\lib\jitsu\package.js:247:10
at c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\node_modules\flatiron\node_modules\broadway
\node_modules\utile\node_modules\async\lib\async.js:94:25
at checkProperty (c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\lib\jitsu\package.js:202:5)
at c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\node_modules\flatiron\node_modules\broadway
\node_modules\utile\node_modules\async\lib\async.js:86:13
at Array.forEach (native)
at _forEach (c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\node_modules\flatiron\node_module
s\broadway\node_modules\utile\node_modules\async\lib\async.js:26:24)
at Object.async.forEach (c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\node_modules\flatiron
\node_modules\broadway\node_modules\utile\node_modules\async\lib\async.js:85:9)
at Object.package.validate (c:\Users\User\AppData\Roaming\npm\node_modules\jitsu\lib\jitsu\package.
js:205:9)
So what is the problem there and how it's possible to solve it?
Related
I'm using the latest version of Meteor (1.4.3.2), the latest version of MUP (1.2.6) and node v6.10.2 but can't get deploy to work successfully. MUP says that everything built, deployed, and started successfully but I get 502 Bad Gateway errors when connecting to my web site. Looking at MUP logs I see that there are problems downloading bcrypt during the deploy and that the app is continuously failing with the following error in mup.js:
/bundle/bundle/programs/server/node_modules/fibers/future.js:280
throw(ex);
^
ReferenceError: module is not defined
at app/mup.js:1:-27
at app/mup.js:59:4
at /bundle/bundle/programs/server/boot.js:303:34
at Array.forEach (native)
at Function._.each._.forEach (/bundle/bundle/programs/server/node_modules/underscore/underscore.js:79:11)
at /bundle/bundle/programs/server/boot.js:128:5
at /bundle/bundle/programs/server/boot.js:352:5
at Function.run (/bundle/bundle/programs/server/profile.js:510:12)
at /bundle/bundle/programs/server/boot.js:351:11
The undefined "module" reference is in the mup.js file that MUP INIT builds: "module.exports = {".
Any suggestions other than don't use MUP? I'm deploying to DigitalOcean running Ubuntu 14.04 x64 vmlinuz-3.13.0-57-generic, not that it should matter.
error in console
shubhabrata#shubhabrata-VirtualBox:~/Meteor/myapp$ mupx deploy
Meteor Up: Production Quality Meteor Deployments
Configuration file : mup.json
Settings file : settings.json
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Meteor app path : /home/shubhabrata/Meteor/myapp
Using buildOptions : {}
buffer.js:80
throw new Error(
^
Error: If encoding is specified then the first argument must be a string
at new Buffer (buffer.js:80:13)
at Readable. (/usr/lib/node_modules/mupx/node_modules/archiver/lib/util/index.js:32:15)
at emitNone (events.js:91:20)
at Readable.emit (events.js:188:7)
at endReadableNT (_stream_readable.js:975:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
Switching from node 7 to node 5.12 worked for me. I installed using nvm so that I can use later node versions in the future.
This occurred for me while using (deliberately) an old version of mup. It could well be that just upgrading mup will fix the problem.
While implementing BDD I developed a test using protractor, cucumber and protractor-cucumber framework.
I don't know what to do with the index.js file.
While running the tests I'm getting the error:
"E/launcher - Error: TypeError: Cucumber.Cli is not a function"
I am using:
cucumber#2.0.0-rc2
protractor#4.0.13
protractor-cucumber-framework#0.6.0
Here is the detailed error message:
[11:22:34] I/hosted - Using the selenium server at http://127.0.0.1:4444/wd/hub
[11:22:34] I/launcher - Running 1 instances of WebDriver
[11:22:37] E/launcher - Error: TypeError: Cucumber.Cli is not a function
at C:\Users\jxm\Documents\Visual Studio 2015\Projects\ProtractorCucumber_FromScratch\ProtractorCucumber_FromScratch\node_modules\protractor-cucumber-framework\index.js:31:16
at Function.promise (C:\Users\jxm\Documents\Visual Studio 2015\Projects\ProtractorCucumber_FromScratch\ProtractorCucumber_FromScratch\node_modules\q\q.js:682:9)
at C:\Users\jxm\Documents\Visual Studio 2015\Projects\ProtractorCucumber_FromScratch\ProtractorCucumber_FromScratch\node_modules\protractor-cucumber-framework\index.js:24:14
at _fulfilled (C:\Users\jxm\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (C:\Users\jxm\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (C:\Users\jxm\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
at C:\Users\jxm\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:556:49
at runSingle (C:\Users\jxm\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:137:13)
at flush (C:\Users\jxm\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:125:13)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
[11:22:37] E/launcher - Process exited with error code 100
I had this problem yesterday - for some reason it doesnt work work when installing cucumber#2.0.0-rc2
I believe its because when installing protractor-cucumber-framework its says : UNMET PEER DEPENDENCY cucumber#2.0.0-rc.2
so seems this version of cucumber is incompatible.
I did: npm install --save-dev cucumber#1.3.1
Then it worked. I believe this is a protractor-cucumber-framework problem
Cucumber#2.0.0 has some breaking changes to the cucumber cli, this is breaking the protractor-cucumber-framework which is written using an older version of cucumber.
An issue has already been logged in the official protractor-cucumber-framework github repo.
Work Around for now would be to downgrade your cucumber version.
I'm trying to run react-native on my machine. I'm using elementaryOS which is based on Ubuntu 14.04. I create base app with
react-native init hello_world
then I try to run this as ios app:
react-native run-ios
this returns me following error:
mateusz#mateusz-L702X:~/hello_world $ react-native run-ios
Found Xcode project hello_world.xcodeproj
/home/mateusz/hello_world/node_modules/promise/lib/done.js:10
throw err;
^
TypeError: invalid data
at WriteStream.Socket.write (net.js:625:11)
at Object.execFileSync (child_process.js:482:20)
at _runIOS (runIOS.js:62:19)
at runIOS.js:24:5
at tryCallTwo (/home/mateusz/hello_world/node_modules/promise/lib/core.js:45:5)
at doResolve (/home/mateusz/hello_world/node_modules/promise/lib/core.js:200:13)
at new Promise (/home/mateusz/hello_world/node_modules/promise/lib/core.js:66:3)
at Array.runIOS (runIOS.js:23:10)
at Object.run (/home/mateusz/hello_world/node_modules/react-native/local-cli/cli.js:87:13)
at Object.<anonymous> (/usr/lib/node_modules/react-native-cli/index.js:88:7)
How can I fix that?
You can build react-native iOS app in Mac only. Using Linux you will not be able to build iOS. Mostly error is related to that.
I'm trying to get meteor reset to work in vagrant box. However I kept getting errors. This is my error message:
/home/vagrant/.meteor/packages/meteor-tool/.1.1.10.8ogiso++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
throw(ex);
^ Error: EBUSY, rmdir '/vagrant/foosboom-meteor/.meteor/local'
at Object.Future.wait (/home/vagrant/.meteor/packages/meteor-tool/.1.1.10.8ogiso++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
at Object.rm_recursive (/tools/fs/files.js:270:9)
at Command.main.registerCommand.name [as func] (/tools/cli/commands.js:1211:9)
at /tools/cli/main.js:1378:23
I'm using hashicorp Otto as my development environment.
I have performed a mount on the local folder as suggested by one of the user here.
Any idea what seems to be the problem? Thanks.
After mounting you can't reset your mongo so do this
sudo umount -f /vagrant/foosboom-meteor/.meteor/local