internalBinding is not defined with version 1.3.0
See original GitHub issueI’m seeing the following error in a travis build with version 1.3.0, any thoughts on what’s going on?
12 12 2018 15:41:47.243:ERROR [plugin]: Error during loading "/home/travis/build/tensorflow/tfjs-core/node_modules/karma-browserstack-launcher" plugin:
internalBinding is not defined
12 12 2018 15:41:47.468:ERROR [reporter]: Can not load reporter "BrowserStack", it is not registered!
Perhaps you are missing some plugin?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
gulp - internalBinding is not defined - Stack Overflow
I ran into the same issue as you. To fix it, I added the following to my package.json in the devDependencies section "natives":...
Read more >SOA Composite Re-deployment Issue - Oracle Support
Oracle SOA Suite - Version 12.2.1.3.0 and later: SOA Composite Re-deployment ... This product might not have a product menu defined in its ......
Read more >Gulp & Npm | ReferenceError: internalBinding is not defined
Gulp & Npm | ReferenceError: internalBinding is not defined. For developing scope, i use “npm” and “gulp” for compile scss , Js, ecc...
Read more >Unity 2022.1.0b9
Scene/Game View: Camera resolution is set to default when opening ... Visual Scripting: 1.8.0 pre-release version is no longer available.
Read more >Open Source Used In CBD 2.3.0 - Cisco
under the Apache License, Version 2.0 (the "License"); * you may not use this file ... and distribution as defined by Sections 1...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI this error doesn’t show up in Node 8 so we switched testing to that environment. This is a problem with Node 10 (and natives 1.1.6 didn’t fix it for me either).
I upgraded to natives 1.1.6 and the problem went away.
npm
makes it easy to not successfully upgrade a package, if your own package is not directly dependent on it. So I’ll detail what I did.Prior to the upgrade, my test suite fails like the description given in this issue, and I’m running
natives
1.1.4:As shown above, the dependency is deep in the tree of packages, so I’m using
--depth=10
to getnpm upgrade
(akanpm up
) to go into the tree. I did not count the depth precisely, I just rounded up to 10. Using a--depth
argument with a large enough value is necessary, otherwisenpm up
won’t fix it. So:The last line shows that
natives
was updated.Let’s check with
npm ls
:Yup, now it shows 1.1.6 and my test suite runs without error.