Skip to content
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

[Bug]: on 1.x, IDE types can sometimes not match ts_project types, causing builds to fail for resolving the wrong type package #1698

Open
Aghassi opened this issue May 3, 2024 · 0 comments
Labels
bug Something isn't working untriaged Requires traige

Comments

@Aghassi
Copy link
Collaborator

Aghassi commented May 3, 2024

What happened?

See this thread https://bazelbuild.slack.com/archives/CEZUUKQ6P/p1714672684183969

I don't have a root cause and it's very hard to nail down what's happening under the hood. From a high level this seems to be something in how node is resolving types in the bazel sandbox being off, but only sometimes. The virtual store looks identical to my .pnpm virtual store, which makes this hard to figure out.

Version

Development (host) and target OS/architectures:

Output of bazel --version:
7.x

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:

Language(s) and/or frameworks involved:

How to reproduce

No response

Any other information?

No response

@Aghassi Aghassi added the bug Something isn't working label May 3, 2024
@github-actions github-actions bot added the untriaged Requires traige label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Requires traige
Projects
None yet
Development

No branches or pull requests

1 participant