"n lts" downgrading npm version 6.10.1 to 6.9.0 #574
Comments
|
What has changed in The install includes both node and npm. This can mean a downgrade of npm if you separately updated npm separately in the default install location. (You could change the npm prefix if you want to manage it yourself.) The default install location used by |
|
@shadowspawn You meant that it's not a new bug, but new feature, right? I do not know why the new feature was adopted. However, if 'n' changes the installation path or re-installs the same version repeatedly, it would be better to notify to the user. |
I mean two things you saw were the same in the previous version. When
See #543 if interested. |
|
@shadowspawn I'm using 'npm-check' to auto-update node modules. I don't know why 'npm-check' updates 'n@5.0.*' today. It is not important in which version the new feature was adopted. Anyway, the newly installed 'n' changes the installation path of my node.js and re-installs my node.js repeatedly, without notice. So, I and my system have been in confusion. It is good to introduce new features and functions to enhance a software. However, it would be better to respect the backward compatibility and the user choice whether or not use new features and functions. You should remember : Though it may be a bad feature, many users are using the feature. |
|
I am sorry you and your system were in confusion. Hopefully you are clearer how it works now. |
|
To make this clearer I am adding the npm version to the install logging in v6. Prerelease available via |
|
Added npm version to install logging in v6: https://github.com/tj/n/releases/tag/v6.0.0 |
Bug Report
Summary
(Please excuse my English)
n lts)Currently node.js LTS version is v10.16.0.
npm -g install npm)I just upgraded 'n' to version 5.0.1, execute
n lts, and I found that 'npm' version was downgraded from 6.10.1 to 6.9.0.At first, I did not know why. But, through the iterative test, I could found that executing
n ltscause the problem. Finally I found that node.js@10.16.0 is repeatedly installed when I executen lts.Additionally, I found that the installation paths of node.js and global modules were changed from ['/usr/bin/node', '/usr/lib/node_modules'] to ['/usr/local/bin/node', '/usr/local/lib/node_modules']. I do not know the reason. But, I re-installed node.js global modules for safety. So two node.js('/usr/bin/node' and '/usr/local/bin/node', all v10.16.0) are installed in my system, currently.
Previous version of 'n' did not make these problems, so I think this is a newly appeared bug.
My system informations
$ n --version 5.0.1 $ node -v v10.16.0 $ which node /usr/local/bin/node $ npm root -g /usr/local/lib/node_modules $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic $ uname -a Linux server 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxThe text was updated successfully, but these errors were encountered: