[Fedor Losev]

Hi, I’m trying to understand how WebClipse is working with Node.

I have a global Node installation.

Window/Preferences
Typescript – my global node.exe
Javascript – mu global node.exe is checked as default

However, terminal seems to use private Users\…\.webclipse\ node installation anyway.

This installation diverges from my global Node. Why terminal doesn’t use my global installation? I don’t want to maintain two diverging copies. Does compiler etc. also use this private installation instead of my Node?

[support-swapna]

Fedor,

The TypeScript page in the Preferences by default is set to the embedded Node.js.
You can change the settings for the Terminal+ to use either the one local to the project or global.

In the Terminal+ view, there is an icon besides the Project field to open the CLI preferences. You can set to ‘System global’ in the opened window. Attached is the screenshot for your reference.

Please let us know how it works for you.

–Swapna
MyEclipse Support

Attachments:

You must be logged in to view attached files.

[Fedor Losev]

Hi, I think local/global is not related to the problem I describe.

I’m talking about configuring global environment.

Say, I have my system node installation in c:\node\ which is in system path, so when I’m working from regular shell node commands are executed there.

Terminal+ uses C:\Users\xxx\.webclipse\nodejs\7.8.0.

If I install something global in Terminal+, it goes to C:\Users\xxx\.webclipse\nodejs\7.8.0\node_modules.

If I install something global in my system shell, it goes to c:\node\node_modules.

Right now I don’t see a way to configure WebClipse to use c:\node\ in Terminal+ and other facilities, so that I can work in Terminal+ and in system shell with the same Node installation and don’t need to ensure two environments are in sync (apart from resorting to symlinks).

• This reply was modified 7 years, 6 months ago by Fedor Losev.

[support-swapna]

Fedor,

In the CLI preferences page that is opened from the Terminal+ view, please uncheck the Node.js version in the ‘Installed automatically’ section. The Terminal+ will now use your global node.js install.

The Compiler uses the install that is specified in TypeScript page under Preferences, which by default is the embedded node.js install unless you set it to your global install.

Hope this helps. Please let us know if you see any issues.

–Swapna
MyEclipse Support

[Fedor Losev]

Thanks, uncheck ‘Installed automatically’ for node/npm in Terminal properties did the trick.

[Author]

Posts