ReferenceError: Node is not defined
See original GitHub issueHaven’t changed anything in my code but reinstalling my dependencies and I now get this error.
Do you have an idea what could cause this?
When I force installing the exact version of all my dependencies, the issue is gone. Will try to figure out which one is causing the issue.
ReferenceError: Node is not defined
at DraftEditorLeaf._setSelection (node_modules/draft-js/lib/DraftEditorLeaf.react.js:87:30)
at DraftEditorLeaf.componentDidUpdate (node_modules/draft-js/lib/DraftEditorLeaf.react.js:105:12)
at invokeComponentDidUpdateWithTimer (node_modules/react/lib/ReactCompositeComponent.js:74:18)
at CallbackQueue._assign.notifyAll (node_modules/react/lib/CallbackQueue.js:66:22)
at ReactReconcileTransaction.ON_DOM_READY_QUEUEING.close (node_modules/react/lib/ReactReconcileTransaction.js:79:26)
at ReactReconcileTransaction.Mixin.closeAll (node_modules/react/lib/Transaction.js:202:25)
at ReactReconcileTransaction.Mixin.perform (node_modules/react/lib/Transaction.js:149:16)
at ReactUpdatesFlushTransaction.Mixin.perform (node_modules/react/lib/Transaction.js:136:20)
at ReactUpdatesFlushTransaction._assign.perform (node_modules/react/lib/ReactUpdates.js:90:38)
at Object.flushBatchedUpdates (node_modules/react/lib/ReactUpdates.js:177:19)
at ReactDefaultBatchingStrategyTransaction.Mixin.closeAll (node_modules/react/lib/Transaction.js:202:25)
at ReactDefaultBatchingStrategyTransaction.Mixin.perform (node_modules/react/lib/Transaction.js:149:16)
at Object.ReactDefaultBatchingStrategy.batchedUpdates (node_modules/react/lib/ReactDefaultBatchingStrategy.js:63:19)
at Object.batchedUpdates (node_modules/react/lib/ReactUpdates.js:98:20)
at Object.ReactMount._renderNewRootComponent (node_modules/react/lib/ReactMount.js:286:18)
at Object.ReactMount._renderSubtreeIntoContainer (node_modules/react/lib/ReactMount.js:365:32)
at Object.ReactMount.render (node_modules/react/lib/ReactMount.js:386:23)
at Object.ReactTestUtils.renderIntoDocument (node_modules/react/lib/ReactTestUtils.js:82:21)
at renderWithOptions (node_modules/enzyme/build/react-compat.js:175:26)
at new ReactWrapper (node_modules/enzyme/build/ReactWrapper.js:94:59)
at mount (node_modules/enzyme/build/mount.js:21:10)
at Context.<anonymous> (message-editor.spec.js:39:25)
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
First time using node.js - "ReferenceError: node is not defined"
Open nodejs: C:\path_of_nodejs>node; Exit from node REPL mode: >process.exit(); You are ready for your node commands: >node -v.
Read more >node.js reference error node not defined · Issue #414 - GitHub
I just installed node.js on my Windows 10 computer. I tried to see the version by typing 'node -v' at the command prompt...
Read more >ReferenceError: node is not defined - General
I have copied couple of nodes between two machines running node red. unfortunately this broke node red and removing npm, node js, deleted...
Read more >ReferenceError: "x" is not defined - JavaScript - MDN Web Docs
ReferenceError : "x" is not defined. The JavaScript exception "variable is not defined" occurs when there is a non-existent variable referenced somewhere.
Read more >node -v ReferenceError: node is not defined - Metahat
node -v ReferenceError: node is not defined. Trying to make node.js work with command node -v and end up with an error.
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
As far as I can tell it is caused by the absence of the definition of global Node.
This will solve the reported Error:
If someone could post how they solved, it’d be great for future reference. Throwing this in there— try using
yarn
instead ofnpm
.