Self tns validation...

I've seen this issue occur the last several times I've upgraded the nativescript command on my Macintosh. I haven't seen this on my windows 7 box.

It installs, and gives me the normal list of all the modules it has installed; but it does not run any of the post-install stuff. However, the install is bad, some modules are missing even though it "appears" like everything installed properly (because of the list of all the modules it just installed successfully is long).

Running TNS will work in some cases; but in most cases depending on which module wasn't installed it will fail at that point with random errors.

I am recommending that on install part of the post install step would be to load each npm module that you are depending upon in a try catch and verify they all exist properly. Then set a flag to the current version. On startup of the tns command, see if this flag is set to the current version, if it isn't set then run this check. In this way you can at least tell the end user that the install is bad and to reinstall tns command.

If others are running into this; it is very confusing why it "appears" to have installed but it is broken in random places. I've learned from using tns for a long time that if it doesn't run the post install checks just to do another "npm install -g nativescript" until it actually runs the post install scripts...

Please note I do realize this could be an issue with my Node/Npm version so I'm going to leave this info here in case others run into this. I plan updating both to the latest 5.x release later so we shall see ...
Node v5.11, npm v3.32

Issue không nêu tên tệp, bài kiểm thử hoặc entry point nào. Hãy bắt đầu bằng cách tái hiện quá trình cài đặt toàn cục trên macOS với Node v5.11 và npm v3.32, sau đó truy vết xem việc xác thực sau cài đặt có được chạy hay không và các module bắt buộc có được tải hay không; công việc được xem là hoàn tất khi cũng có tín hiệu lỗi rõ ràng nếu quá trình cài đặt chưa hoàn tất.