I'm trying to start project with JHipster 6. Unfortunately every single command I give cause long (3-10 Minutes) lag.
E.g. when I type
jhipster --verbose
INFO! Using JHipster version installed globally
I have to wait until something will appear on the screen. Is there any possiblity to enable tracing?
OS: Win10 64bit
node: 12.16.2
npm: 6.14.4
This is due to the bug https://github.com/jhipster/generator-jhipster/issues/11617
Already fixed in https://github.com/jhipster/generator-jhipster/pull/11618 and will be available in a newer versions
Related
I am building a sample application in which I need to use Node Version v9.11.2 and npm 4.0.0. Currently I have Node Version v16.4.0 installed on my system. I tried to install the specific version by uninstalling the latest version and installing version 9.11.2 from official website
Problem: The problem is I can uninstall the latest version without any problem but when I try to install older version(9.11.2) the command gets opened and it does nothing. I also tried to install the older version using cli commands ie. npm install -g node#9.11.2, it installs the version but on checking the version using node -v, it still shows the latest version(16.4.0)
Below are the screenshots for better understanding
Installed version 9.11.2 but showing 16.4.0
Any Solution please ?
Is using docker a possibility? If so you can simply get a docker image of the required version and use if from there.
Another way is to use NVM which is a really useful tool to manage nodejs versions. I'm including their github repo for your convenience:
https://github.com/nvm-sh/nvm
A good option is to use NVM: https://github.com/coreybutler/nvm-windows (Windows) or https://github.com/nvm-sh/nvm (unix, macOS). With NVM you can enable different versions of node on the same machine and switch from one to another, usually it takes care of managing the installed packages and adding them to its own management system.
I am quite new to NodeJS and am planning to upgrade NodeJS version for my current project. The most recent NodeJS LTS is installed using NVM.
I need to keep switching between the current LTS that i am using and the new LTS that has been installed. I understand that i can do 'NVM use' for this purpose. npm-shrinkwrap.json is being used to lock down the npm package dependencies.
I am planning to follow the below approach both in my dev machine and build machine;
Is it okay? If not, please suggest a best approach.
nvm use latest_LTS
Update the package.json to pick the version which is supported by
latest_LTS
npm install
generate testing_build
Whenever i need to generate a build for current release (with the previous LTS NodeJS)
nvm use currently_used_LTS
clear the node modules
npm install (Release npm-shrinkwrap.json)
generate release_build
Thanks
In theory that should work.
However have you considered the option of just doing a point release for the current release_build that does nothing except version-bump node?
You may find (after re-running your tests) that the latest version of node is backwards compatable with release_build (or only requires minor fixes), and you can simplify your life by porting everything to the latest node version, rather than constantly switching
I use a Windows 10 x64 Pro machine as a development environment.
Today I went to the Node.js site, (nodejs.org/en/download) to get the LTS version which is 8.11.4 for Node and includes npm 5.6.0. This information is visible at the top of the page.
After installation, I did the command "node -v" and actually this gives me v8.11.4 as result. On the other hand the same command for npm "npm -v" gives me version 2.15.10.
What troubles me is that different documentation suggests that the update is done by installing the latest version, which I did, with the result that I have; the wrong NPM version.
I need at least NPM version 3.x or higher. As a lead already explored without success;
- clean installation from the original site by choosing the LTS version, branch x64
- uninstalled the version and reinstalled
Is it a known bug or is there another avenue to explore?
The short version is: VS 2017 installs a really old version of NPM.
By doing the following command in powershell "npm config get prefix" I could see that the prefix was pointing to Microsoft. Then I used the "npm-windows-upgrade" tool to get the installer path for VS. From there I navigated to the bin folder and launched the JavaScript file to start the update.
VS2017 looks to use version 2.15.10.
The path to it is c:users{userprofile}.mpmrc
I just deleted this file and all ran fine (i'm not using VS).
I have a restriction of using node JS version 6.9.1. I am getting many problems, while using angular cli quick start steps.
after ng serve, browser page will be white, no error in console.
npm start works, but if i change some style/file browser do not not refresh.
if i make any style change, webpack compiled successfully message comes but webserver fails to load page.
When I follow the quick start steps with latest nodejs it works like a charm. Can any one help me in telling, what are the versions (npm, angular-cli), I should use to run it ?
Like
Each Angular/Cli version has limited its compatibility of node versions below a specified release. If you have to use a specific version of node then your best bet would be to find a previous version of the Angular/Cli that will play nicely.
Here you can find all the versions and from there, pick one a little further back in the list and then do a search in google for "Angular/cli version x.x.x node compatibility" to see if there are any known issues.
Once you pick a version that looks good, run
npm install -g #angular/cli#<your version number>.
Once the install is complete run ng help and you'll get feedback right away if the version is still incompatible and you can try a different version.
Just make sure you get rid of the installs you aren't using with npm uninstall -g #angular/cli#<your version number>
for see if angular-cli is compatibility whit your node version installed you can see https://www.npmjs.com/package/#angular/cli/v/6.0.8?activeTab=versions, for example, I have installed node 6.11.2 and I have to use: npm install -g #angular/cli#6.0.0
When I use "brew upgrade node"
brew upgrade node Warning: You are using a pre-release version of
Xcode. You may encounter build failures or other breakages. Please
create pull-requests instead of filing issues. Error: node not
installed
But when I use "brew info node"
Please note by default only English locale support is provided. If you
need full locale support you should either rebuild with full icu:
brew reinstall node --with-full-icu or add full icu data at runtime
following:
https://github.com/nodejs/node/wiki/Intl#using-and-customizing-the-small-icu-build
You have a fully functional version of node.
Try it for yourself and see what you get. I would expect something like:
> which node
/usr/local/bin/node
> node -v
v6.7.0
The first error is the interesting bit. Looks like you are on xcode 8.0 before it was released and maybe it did cause issues with upgrading node. I presume with the public launch of xcode, this is no longer an issue.
The brew info node caveat is just letting you know that you have a working version of node, but with english only.