Cannot read property 'equal' of undefined
See original GitHub issueHello, nanobus
doesn’t work in browser. Why do you use Node API?
var assert = require('assert');
will break code for browsers.
The same for nanotiming
. You assure that lib will work in browsers but it’s wrong (from nanotiming
README: Works both in the browser and Node)
nanoscheduler
has nanoassert
as dependency and as I understand for browsers you replace node
’s assert
with your nanoassert
using package.json
browser field:
"browser": {
"assert": "nanoassert"
},
Am I right?
Thanks
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
TypeError: Cannot read property 'equal' of undefined
javascript - TypeError: Cannot read property 'equal' of undefined - Stack Overflow. Stack Overflow for Teams – Start collaborating and sharing ...
Read more >TypeError: Cannot read property 'equal' of undefined #5 - GitHub
Hi,. That error occurs when I run these tests (occurs as well when I use shallow):. it("length is = 1", function() { expect(render(<Component...
Read more >Cannot Read Property of Undefined in JavaScript - Rollbar
Undefined means that a variable has been declared but has not been assigned a value. In JavaScript, properties and functions can only belong...
Read more >TypeError: Cannot read property 'equal' of undefined-Reactjs
Coding example for the question TypeError: Cannot read property 'equal' of undefined-Reactjs.
Read more >typeerror: cannot read properties of undefined (reading 'equal')
Here's an example of a JavaScript TypeError: Cannot read property of undefined thrown when a property is attempted to be read on an...
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 Free
Top 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
@ok2ju hmmm, it sounds like this isn’t so much
nanobus
specific, as it’s a an issue withrollup
. I think this issue in itself might be enough to help point people in the right way.hmm, I thought rollup-plugin-node-resolve would respect the browser field when setting the
browser: true
option, but it looks like it’s not working correctly.You can get the same browser versions of core modules as browserify uses with the node-builtins plugin.