Compiling Node 0.4.7 on Ubuntu 11.10? - javascript

I'm trying to compile 0.4.7 for Heroku support, but I can't seem to get ssl support working, which express requires.
I've installed libssl-dev, and even tried to install openssl by hand, but nothing seems to get this working. What do I need to do to get node running?
Waf: Leaving directory `/home/skendall/node/node-v0.4.7/build'
Build failed: -> task failed (err #1):
{task: cxx node_crypto.cc -> node_crypto_4.o}

Use v0.4.9 will resolve this issue.

To get node-v0.4.7, or any other version before node-v0.4.12, working with ubuntu 11.10 will involve modifying the source code of node.
Specifically src/node_crypto.cc, which requires the removal of checks for any ssl methods other than sslv1. this section is roughly located around line 100 in the file.
Once done, follow the usual: ./configure; make; make install
This change was tested and worked with express lib, on ubuntu 11.10 with openssl compiled without sslv2.

Related

Error when trying to run JS in VScode for the first time (newbie)

So i just installed VScode on my Windows 10. I keep getting the following error:
"Can't find Node.js binary "node": path does not exist. Make sure Node.js is installed and in your PATH, or set the "runtimeExecutable" in your launch.json"
I've tried reinstalling VS and rebooting, tried installing from different folders (both on C drive and the second time i added it to my programs folder)
I tried installing a node.js extension which fails every time and then prompts me to try it manually...which then leads to a file downloading automatically, but when i add it to my VS folder through my file explorer, nothing happens still.
I tried installed a different node.js debugger
I tried changing my debugger to chrome too but all it does is take me to localhost:8080 and an empty page of course.
When i go through file explorer and look through the path of my .vscode folder, the nightly extension (node.js) is there....
I'm new to VScode and have just been using Scrimba's terminal to do my code but decided to try something more professional
I think you're putting node.js in the same folder/path as .vscode, this isn't correct. What you need to do is set node.js in your PATH which is different. See this answer for more information on how to set PATH/environment variables. Also install it from the official website nodejs.org. After changing your PATH remember to reboot.
I wouldn't recommend downloading "node.js extensions" as those likely are not legitimate, and as you've said yourself they don't work. Only download from the official website.
You have to install nodes from this website https://nodejs.org/

Windows builds of an Electron app on Cent OS 64 bit with electron-packager fails with error

I'm trying to set up build on a remote Cent OS server and stuck with error. I installed wine, but since the server has 64-bit architecture, wine command is wine64, not just wine. Each time I try to make a Windows build, I get the Could not find "wine" on your system... Make sure that the "wine" executable is in your PATH. error. It seems like it's trying to execute "wine" command, but I have "wine64" instead, and according to various guides, it's ok. Making an alias didn't help.
Could someone suggest how I can workaround this issue?
Thanks.
I was getting the same error:
Packaging app for platform win32 x64 using electron v4.2.12
Could not find "wine64" on your system.
Wine is required to use the appCopyright, appVersion, buildVersion, icon, and
win32metadata parameters for Windows targets.
Make sure that the "wine64" executable is in your PATH.
See https://github.com/electron/electron-packager#building-windows-apps-from-non-windows-platforms for details.
Running these steps in terminal, allowed me to resolve this issue:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew doctor
brew cask install wine-stable
Source: https://www.davidbaumgold.com/tutorials/wine-mac/
As it turned out, I built only 64-bit version, but I had to build and install 32-bit version as well. Even though compilation and installation went with warning that some 32-bit stuff is missing, the electron builds seem to be OK and work OK.
The tutorial I finally followed is here.

Running selenium with Javascript on Node.js

I am a noob to Javascript so apologies if my question is very trivial.
I am trying to run a selenium test that was wrote in Javascript. As I usually do, I just want to start with something simple and work from there. In my script I am just trying to load Google using chromedriver.
var webdriver = require("selenium-webdriver");
var driver = new webdriver.Builder().withCapabilities(webdriver.Capabilities.chrome()).build();
driver.get("http://www.google.com");
On the CLI I navigate to the directory where the Test.js file is saved in and I run the command node Test.js. I always get this error in response;
C:\Selenium\node_modules\selenium-webdriver\_base.js:104
vm.runInContext(opt_srcText, closure, src);
^
SyntaxError: Unexpected token )
at goog.loadModuleFromSource_ (C:\Selenium\node_modules\selenium-webdriver\l
at Object.goog.loadModule (C:\Selenium\node_modules\selenium-webdriver\lib\g
at C:\Selenium\node_modules\selenium-webdriver\lib\webdriver\promise.js:1:6
at Object.Context.closure.goog.retrieveAndExecModule_ (C:\Selenium\node_modu
at <anonymous>:1:6
at Context.closure.closure.vm.createContext.CLOSURE_IMPORT_SCRIPT (C:\Seleni
at Object.goog.importScript_ (C:\Selenium\node_modules\selenium-webdriver\li
at Object.goog.importModule_ (C:\Selenium\node_modules\selenium-webdriver\li
at Object.goog.writeScripts_ (C:\Selenium\node_modules\selenium-webdriver\li
at Object.goog.require (C:\Selenium\node_modules\selenium-webdriver\lib\goog
I originally ran this code on my Windows machine and when I was getting that error I put it down to Windows and Node.js no agreeing and tried it on my Mac. Still no luck as I was getting the exact same response.
On both machines I have node and npm installed. Previous to executing the tests I ran the command npm install selenium-webdriver and I also added chromedriver to my PATH.
I have no idea what I am doing wrong so if anyone can point me in the right direction, it'd be very much appreciated.
Turns out the version of node I was using was too old.
Thanks to #Louis for your help in reaching this solution.
What I did was uninstall node and re-installed it with the latest version. I would imagine upgrading would work too.

Cannot run Meteor js 1.1 on windows 8.1

I have tried to install meteor js 1.1 on windows 8.1 with the official installer:
https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows
But even after restarting my computer, when I type the command meteor in the command prompt I get the error command not found.
Even after a search on my computer to find the installation folder of meteor, I am unable to find the answer. However, in the add/remove program utility, I can see meteor.exe.
As a note, I already successfully installed meteor before, and it used to run smoothly. In the meantime, I have removed and re-installed node, and it seems that since this moment the command meteor does not work anymore. Hence my attempt to re-install it.
Does anyone have any idea about how to troubleshoot my issue ?
I just solved my issue by using the windows command prompt instead of the git bash
It appears that only windows command prompt is supported so far.
You can try to manually add Meteor to your Path.
Go to "Environment variables" (you can find it by doing a simple search in your welcome screen) and add the following entry:
C:\\Users\\**your_user_name**\\AppData\\Local\\.meteor
Do not forget to separate this entry from other entries by a semicolon ;.

Installing Nodejitsu

I have successfully installed NodeJitsu using NPM. However, anytime I attempt to run it I get the following error:
TypeError: Arguments to path.join must be strings.
It happens at line 204 in path.js
Any ideas?
We are working on release our toolset with node 0.10.0 support, you can use it with the last 0.8.x branch (0.8.22). We will publish a new version as soon as possible.
This issue is fixed internally but we are working on all the possible points of failure in node 0.10.0.
Stay tunned for updates!
If you need support you can join #nodejitsu on Freenode ;)

Categories

Resources