We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Being able to run jovo CLI commands without having a package-lock.json
jovo
package-lock.json
Through some digging, we realized that there's checks for package-lock.json. So it keeps throwing:
To use this command, please go into the directory of a valid Jovo project.
Our project doesn't need a package-lock.json
I feel like these checks are unnecessary.
The text was updated successfully, but these errors were encountered:
Hey @jakelevi
I tried it with jovo v4 and jovo v3, but I can't reproduce it.
$ jovo3 new foobar $ cd foobar $ rm ./package-lock.json $ jovo3 run
Do you have an example?
Sorry, something went wrong.
No branches or pull requests
I'm submitting a...
Expected Behavior
Being able to run
jovo
CLI commands without having apackage-lock.json
Current Behavior
Through some digging, we realized that there's checks for
package-lock.json
. So it keeps throwing:To use this command, please go into the directory of a valid Jovo project.
Our project doesn't need a
package-lock.json
I feel like these checks are unnecessary.
Error Log
Your Environment
The text was updated successfully, but these errors were encountered: