-
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
Is there some way to surpress this warning message? #5349
Comments
The 1st warning is also a little strange... it's something inside of tfjs causing that. |
@TylerLeonhardt what environment are you running in? seems both of the flags IS_BROWSER and IS_NODE are true.
|
@pyu10055 within VS Code. My guess is that since it's an electron app... both return true. You can test this by opening up the dev tools in VS Code: |
@TylerLeonhardt in this case, you can just use webgl backend by not including tfjs-backend-cpu package. |
@pyu10055 thanks for the pointer! I believe you said CPU is best in our use-case in the previous issue, so I'm trying that.
to
Unfortunately, this still yields the logs in the original screenshot. For your reference, the code in question is found here: https://github.com/Microsoft/vscode-languagedetection |
@TylerLeonhardt can you try to set
|
@pyu10055 That gets rid of the "hi there 👋 " log, great! The last one that shows up is:
which only shows up when running in VS Code... (in electron, I guess)... in my mocha tests in the vscode-languagedetection repo I do not see it. |
Thanks for this @pyu10055! |
Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information
Describe the feature and the current behavior/state.
👋 from the VS Code team
We use tfjs in VS Code and see this warning:
It would add a lot of extra complexity to include tfjs-node in VS Code so we'd like to not do what it's suggesting and instead would like to suppress this warning.
Is this possible?
Will this change the current api? How?
No
Who will benefit with this feature?
People who don't want to use tfjs-node
Any Other info.
The text was updated successfully, but these errors were encountered: