-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Compile error with @tensorflow/tfjs-backend-webgl for TS target > ES5 #4201
Comments
Does this happen with |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you. |
No, and I get it that it's part of the official docs to place this flag in case of an error, but our case doesn't allow skipping lib checks |
In that case you may need to wait until we upgrade the version of typescript we compile with. We are planning on doing that in the nearish future but I can't give you an ETA on that. I think this is caused by a clash between the now built in types for webgl and the @types/webgl2 package we currently use. |
Bumping this, there's a new version of @types/webgl2 that's supposed to fix the bug. Since tfjs-backend-webgl pinned the dependency to version 0.0.5, we can't upgrade @types/webgl2 without changing tfjs-backend-webgl. |
Any news on this? |
The errors still occur with the latest version of
The errors are the same as in the first post. About the `long` moduleNote that I also added `long` module and types because otherwise I get these errors:
|
I just ran into this bug. We've upgraded to TS 4.8.4, so I think we can remove |
Remove @types/webgl2 since ts4 includes these types in lib/dom. Fixes tensorflow#4201
Remove @types/webgl2 since ts4 includes these types in lib/dom. Fixes #4201 Co-authored-by: ahmedsabie <[email protected]>
System information
Describe the problem
When trying to build a typescript code that depends on
@tensorflow/tfjs-backend-webgl
, if thecompilerOptions.target
is above ES5 (i.e "ES2015","ES2016","ES2017","ES2018","ES2019","ES2020" or "ESNext"), you get the following compilation errors:Provide the exact sequence of commands / steps that you executed before running into the problem
The error is easily reconstructed with the following:
Any other info / logs
This partially relates to #2007 but not the same issue
The text was updated successfully, but these errors were encountered: