-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testyts command not on the path despite a seemingly successful installation #76
Comments
Further analysis: testyts is well present in ./node_modules/.bin with a correct link. The link points to the correct js file but this file refuses to execute. (NOTE: my current Ubuntu install is fairly recent - a few weeks - and I had to install it from scratch. The system is therefore in a fairly "pristine" state regarding installed packages but the Nodejs ecosystem is present and working). bin directory is on the PATH and other commands are working. Console activity (terminal, outside of VS Code) :
|
Problem seem to come from virtual node environments. The bin directory on the path is not the project's one but one from nvm:
|
Still puzzled. With -g, testyts has well been installed:
... but it is not linked in .bin/
Nor is it present in the ../lib subtree:
|
Linking from .../nvm/... to the executable does not solve the problem :
Executing the command as root does not help:
|
Installation problem (namely that testyts does not appear anywhere on the PATH remains unsolved (and I don't exactly know how to solve it) but I have a workaround consisting in directly invoking testy.js under node_modules. :-( For now, I will proceed so, in order to evaluate TestyTs. If successful, I can contemplate contributing to Testy by fixing this installation problem. Any hint welcome. |
Hi! Sorry I haven't had time to look into that yet, thanks for the detail level though, I appreciate! I'll try and look into that as soon as possible. Another workaround would be to install |
Yes, defining "test" under "scripts" as "node node_modules/testyts/build/testy.js" works as a workaround. I remain interested in a more permanent fix, of course ;-) |
Have you tried invoking |
OS: ubuntu 20.04 LTS
npm: 7.11.1
Global install does not work any better :-(.
Package is well present under node_modules. What can be wrong?
The text was updated successfully, but these errors were encountered: