-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Types are only made available when explicitly added in tsconfig.json #111
Comments
For clarity, |
Just a heads up that this is present in |
Okay, I dug a little further and what I thought was the issue ... wasn't. I've made a repo here: https://github.com/paullewis/repro-rules-ts-issue-111 According to the TS docs any If, however, I explicitly add All very confusing to me, really. Setting the |
I sorted a temporary workaround: set |
@paullewis could you try with https://github.com/aspect-build/rules_ts/releases/tag/v1.0.0-rc1 and see if the issue persists? |
Yes, that seems to fix it - thank you! I'll close the Issue. Out of interest, what was the cause? |
The worker mode virtual file system @thesayyn wrote wasn't following the |
Was fixed by #125 |
I see - thanks for the info! |
Hey,
Was just trying the 0.11.0 prerelease, and thought I'd let you know of an unusual behavior (in case you don't know!).
Supposing you have a
BUILD.bazel
file like this:It doesn't really matter what you have in
src.ts
, but supposing the following is insrc.test.ts
:You'll get the following error when trying to build
:src_test
:It seems the double dep of
"//:node_modules/@types/node"
in both:src
and:src_test
is the root of the issue, though I'm not at all sure why. Removing@types/node
from:src
will prevent the error from emitting, but that doesn't seem like the right fix!The text was updated successfully, but these errors were encountered: