-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Cannot find name 'Buffer' #978
Comments
You can either:
|
Already on latest node and the errors still appear. And skipLibCheck
affects all libs which I would love to avoid.
…On Tue, 28 Jan 2025, 03:59 LongYinan, ***@***.***> wrote:
You can either:
- add skipLibCheck: true to your tsconfig.json
- or npm i --save-dev @types/node
—
Reply to this email directly, view it on GitHub
<#978 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEICW32TUEUBDYLYP2YQKR32M3W7PAVCNFSM6AAAAABV6WUOW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJXG4ZDSMRZGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Have you tried |
Yes that is what I meant.
I am still debugging this. I created empty angular 19 repo and have not yet encountered the same issue. |
Here is the repro https://stackblitz.com/edit/node-apbsp4rj?file=tsconfig.json skipLibCheck works but is not desired. |
@MikeDabrowski add |
No, adding I have modified the stackblitz and still getting the same error. The only workaround that works is |
@MikeDabrowski I don't have any typecheck issues in your stackblitz project anymore
I have tried with pure npm/TypeScript project and it works fine, so I don't think it's a bug from |
@Brooooooklyn It is really weird. I also no longer have this errors in the stackblitz. Even after removing I just did a check in my project. I removed In the stackblitz I fixed all versions and tried again with no types and no skipLibCheck - still passes. But in my project I need to have I can't explain what happened, but as you said - |
We are using pdfjs which uses this lib. Recently we are trying to update to latest version which runs on typescript 5.7. But the builds do not work because of this bug. Is there any workaround ?
Our project already has latest node typings and
"@types/node": "^22.10.10",
Here are the error examples:
The text was updated successfully, but these errors were encountered: