nodist `0.8` seems like changed naming rule of node directory
iulo opened this issue · comments
upgrade form 0.7.2 to 0.8
nodist seems like install 6.x by itself. and the naming rule of node directory changed .
C:\Program Files (x86)\Nodist\v
├─6.2.2
├─nodev0.12.2
├─nodev4.0.0
├─nodev4.2.3
├─nodev4.2.6
├─nodev4.4.0
├─nodev4.4.4
├─nodev5.3.0
└─nodev5.5.0
I get an error Sorry, there's a problem with nodist. Couldn't resolve version spec %s: %s nodev4.4.4 improper constraint: nodev4.4.4
solved.
edit .node-version from ‘nodev4.4.4’ to 4.4.4
nodist dist return list weird.
The order is unordered
...
1.5.1
5.9.0
1.5.0
5.9.1
1.4.3
5.10.0
1.4.2
5.10.1
1.4.1
5.11.0
1.3.0
5.11.1
1.2.0
5.12.0
1.1.0
6.0.0
1.0.4
6.1.0
1.0.3
6.2.0
1.0.2
6.2.1
1.0.1
6.2.2
1.0.0
0.8.8
Hi!
Sorry for the inconvenience. I added some upgrading instructions to make sure the nodist directory is completely removed before installing v0.8 and added a note about the possible necessity to re-set local node version settings.
I also created #152 for the dist sub-command bug.
does that mean node_modules dir will be delete ?
@marcelklehr I totally reinstall nodist 0.8.1 , but the version sorting still weird.
Do you have any other way to upgrade from 0.7.x to 0.8.x ? I have a lot of global module, Now I have to reinstall them. I feel terribile now 😭
I'm sorry :( To be precise, only deleting the .node-version file, bin/npm.cmd, bin/node_modules/npm/ and the v/ and v-x64/ dirs is necessary, iirc. It might make sense to separate nodist's binaries from the globally installed npm packages, in order to avoid such problems in the future. See #154 for this.
The fix for version sorting in the nodist dir output is not released yet. v0.8.1 fixes some other issues.