-
Notifications
You must be signed in to change notification settings - Fork 30
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
lerna error while testing #829
Comments
Can you please provide more information about your environment? |
git-bash and Powershell I tried running the above command in both and got the same error. |
Your previous image has some more information You may be the only person with this setup that could properly reproduce and fix this bug. I found this issue that could be related. But my bet would be with the escaping slash. Please try this change in package.json - "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c \$LERNA_ROOT_PATH/.npmpackagejsonlintrc.json .",
+ "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c \"${LERNA_ROOT_PATH}\"/.npmpackagejsonlintrc.json .", or this - "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c \$LERNA_ROOT_PATH/.npmpackagejsonlintrc.json .",
+ "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c '${LERNA_ROOT_PATH}/.npmpackagejsonlintrc.json' .", and run: npm run test:packagelint |
@hugosenari still getting the same error. |
The problem is with window's file path which is different from that of Linux, which I guess you guys have already figured out.
Following is the link on how to install WSL2 and node. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior. MVCE would definitely help.
npm test
from root inWindows 10 pro
Screenshot
The text was updated successfully, but these errors were encountered: