-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
NotFound: No such file or directory #135
Comments
After some more testing, I found out this is due to the npm entries. |
Hi, sorry for the late response we've been kind of busy and some features of trex got broken in some deno updates and we need to update and fix trex (actually the output of trex --version is because this file is out of date https://github.com/crewdevio/Trex/tree/master/utils ) |
oh, alright. when will there be a fix for this? |
I'm going to keep an eye on it to see if I can do something, but any PR is also welcome, I'll take care of reviewing it and mixing it |
fix: skip hash generation or hash validation for npm dependencies #135
Trex was trying to read npm dependencies as a local file path to generate a hash and check the file integrity. For now we are not checking npm dependencies until #134. The fix is already released. |
Describe the bug A clear and concise description of what the bug is.
When running
trex install --map fs
with my own entries in import_map.json, an error is produced sayingNotFound: No such file or directory
.To Reproduce Steps to reproduce the behavior:
trex install --map fs
results in error sayingAfter some more testing, I found out that its import_map - when I run it with an import_map which doesn't have my own entries within it, no such error is produced.
import_map.json
Expected behavior A clear and concise description of what you expected to
happen.
To install without an error.
Screenshots If applicable, add screenshots to help explain your problem.
(trex also consumes extra lines when running
trex install
)Desktop (please complete the following information):
some version bug? it says I upgraded to 1.12.0 when using trex upgrade --canary but trex --version outputs 1.11.0.
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: