-
-
Notifications
You must be signed in to change notification settings - Fork 301
./integration-tests/yarn-workspaces/yarn-workspaces.test.ts fails #255
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
Comments
It seems package/a/ is supposedly a sub-project. With it own package.json and node_modules/. How was this to come about? Is it missing from this script? |
OK, I've just learned about yarn workspaces 😄
I'm pretty sure all I can make a PR for this. This includes the invocation at patch-package/integration-tests/yarn-workspaces/yarn-workspaces.sh Lines 14 to 15 in 50f73bd
also is supposed to be yarn patch-package left-pad ? But here, npx just happens to work.
|
I've noticed in all other integration-tests/ |
Uh oh!
There was an error while loading. Please reload this page.
Running
yarn test .*/integration-tests/yarn-workspaces/yarn-workspaces.test.ts
produces these results.Digging through the logs, I've narrowed down the root-cause to this line.
patch-package/integration-tests/yarn-workspaces/yarn-workspaces.sh
Lines 20 to 22 in 50f73bd
I suspect
npx
simply downloads the released version of patch-package (which still has issue #181 #253)Tests should use the current/working version? Not the one in the NPM registry.
The text was updated successfully, but these errors were encountered: