Closed AArnott closed 1 year ago
+1
@scruel tip: use a github thumbs up reaction to the original issue rather than posting +1
in a comment. It aggregates much better, giving the repo maintainers a quick idea of size of interest.
@AArnott Ok, thank you for your advice.
I had the same issue. "npm update -g" fixed it for me. I had a slightly older typescript and updating seemed to resolve the issue.
@chapma26 given this no longer repros for me, I suspect you may be right. Although I'm disappointed that it would use the global tsc npm package instead of a local one, for many reasons including avoiding an issue like this.
Never mind. It no longer repros for me with a new yo code
directory, but my existing one where it was failing before still fails, even after ensuring I'm using the latest typescript compiler. I suspect something has changed in the yo template to fix this, but diffing the latest against what I had when I filed this, I can't find any significant change.
It was a bug in @types/node: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62672
Does this issue occur when all extensions are disabled?: Yes/No
yo
extension template problem)Steps to Reproduce:
yo
yo code
and indicate that you want to create a new VS Code extension (TypeScript). Complete the interview process (I used yarn).yarn pretest
Expected
Successful compilation
Actual
Compilation failure:
The 'fix' I've found is to add
dom
to thecompilerOptions.lib
array intsconfig.json
. But shouldn't the template compile out-of-the-box?