-
Notifications
You must be signed in to change notification settings - Fork 440
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
Issue with related path #92
Comments
Yeah, it seems it's expected. Off-topic, in case the package.json is not in root because it's a monorepo, I've got a monorepo and I use Lerna and cz and all works fine. See https://gitlab.com/codsen/codsen — I'm happy to advise, my email is public. Looking realistically, I see two possible outcomes: 1) if we want to pursue the path to support package.json not in root, we need to describe the use case better — put more details; 2) if it's a monorepo issue, maybe the problem can be solved without requesting changes in cz? Please give more details, somebody will help. Or if the issue has been solved since please let us know so we can close. Thank you 👍 |
Hello! It looks like that tool expects that pakage.json is located in repository root folder. In my case it is not and I got "Cannot find module" error. Is it expected behavior?
The text was updated successfully, but these errors were encountered: