How to avoid the redundancy of running TypeScript binaries under @yarnpkg/pnpify
?
#5069
Unanswered
wizardlink
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Have you found a solution? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'll be as brief as I can, considering I am quite mad at this lack of documentation and explanation as to why this is needed and why it even is an issue.
On a clean project I've added:
typescript
,@types/node
and@yarnpkg/pnpify
, my entry point isout/index.js
and the source file issrc/index.ts
.In the source file all I have added is a simple
console.log(':)')
and to transpile it I have ranyarn tsc -p ./
which that spews me the error:If I run under
pnpify
(yarn pnpify tsc -p ./
) I get these obscure nonsense:Then I decide, ok, I'll explicitly add in my
tsconfig.json
thatnode
is one of the typings I have, but when I runyarn tsc
or even directly.yarn/sdks/typescript/bin/tsc
I get the following:But under
pnpify
in this case it transpiles with no complaints whatsoever, so my question is: Why is the sdk that yarn bundles has this issue? From what I can tell too when talking to my friends, no one that is running under Windows has this issue but some people in Linux do, but not everyone.Does anyone knows why this is the case and if there is a workaround? Because having to explain to research and explain how to integrate
tsserver
,eslint
,prettier
and any other toolset in each kind of editor we may use through this will be hell.Beta Was this translation helpful? Give feedback.
All reactions