Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"Unable to find project at ..." error #72

Closed
Fishrock123 opened this issue Feb 25, 2019 · 3 comments
Closed

"Unable to find project at ..." error #72

Fishrock123 opened this issue Feb 25, 2019 · 3 comments
Labels
Sev3 Type: Bug
Milestone
Sprint 13 (4/30 -...

Comments

@Fishrock123
Copy link
Contributor

X Unable to find project at: /Users/Jeremiah/Documents/here-be-dragons

This directory has node_modules but no package.json. I think that universal-module-tree should be able to be forced to run regardless.
@Jazneil
Copy link

Jazneil commented Apr 4, 2019

Hey @Fishrock123 can you please add priority and an estimate to this bug?

@juliangruber
Copy link
Contributor

universal-module-tree can't run properly in that case because it won't be able to distinguish toplevel from sublevel dependencies, and therefore can't build a dependency tree.

We might support this in a new flat mode however, if you think that's useful?

@Fishrock123
Copy link
Contributor Author

@juliangruber While that would be ideal, for now the error message is wrong.

We don't intercept the error from u-m-t correctly, which should say that an install has not been done.

@Fishrock123 Fishrock123 added this to the Sprint 12 (4/9 - 4/29) milestone Apr 5, 2019
@Fishrock123 Fishrock123 added this to the Sprint 13 (4/30 - 5/20) milestone May 16, 2019
Fishrock123 added a commit that referenced this issue May 16, 2019
@Fishrock123
report: do not obscure analyze errors
23f4871 
Ensures we print the error message from analyze, since usually it has better information on what occured.

Fixes: #100
Fixes: #72
@Fishrock123 Fishrock123 mentioned this issue May 16, 2019
Merged
Gioyik pushed a commit that referenced this issue Apr 22, 2020
@Fishrock123 @Gioyik
report: do not obscure analyze errors
166b984 
Ensures we print the error message from analyze, since usually it has better information on what occured.

Fixes: #100
Fixes: #72
PR-URL: #150
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Sev3 Type: Bug
Projects
None yet
Milestone
Sprint 13 (4/30 - 5/20)
Development

No branches or pull requests
3 participants
@juliangruber @Fishrock123 @Jazneil