-
-
Notifications
You must be signed in to change notification settings - Fork 936
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
Regression: pnpm link
with workspace references fails
#6603
Comments
Workaround: Pinning the version sam-goodwin/eventual@41a32f6 |
Also in v7.33.0 |
ok, can someone create a smaller repository that reproduces the issue. I don't understand what is happening. This change might be related: #6598 |
I came to this issue because that happen to me in version
It became clearer that my problem was a bad name in the Probably not @thantos issue, but I hope it can help some people and detect false cases. |
Hello @zkochan, although it is slightly different from the Steps to reproduce
|
I'm not sure if this is the same error, but I ran |
I got the same error, did you find a way to resolve it? |
What do you mean a name problem? I got the same error. |
@zkochan would be cool to get this one on the priority list. currently preventing me from setting up a proper test environment for CI for jsx-email. Looks like #6603 (comment) provides a solid reproduction. |
Just got the same EDIT: Found this, might be related: swc-project/swc#8988 |
pnpm version: 8.6.0
Code to reproduce the issue:
https://github.com/functionless/eventual/blob/main/apps/tests/aws-runtime/scripts/test-create
Test script that links workspace packages over a local install.
Expected behavior:
link
should succeed. It succeeded with 8.5.1 and has worked since 6.* at least.https://github.com/functionless/eventual/actions/runs/5100583453/jobs/9169107938#step:4:23
Actual behavior:
Github action picked up the latest 8.6.0 and now throws this error:
https://github.com/functionless/eventual/actions/runs/5104922608/jobs/9176183671?pr=379#step:4:25
Additional information:
node -v
prints:18.16.0
The text was updated successfully, but these errors were encountered: