Webpack or Rollup transpilation error - TypeError: Right-hand side of 'instanceof' is not an object
See original GitHub issueIt looks like the name of the function attached to ctor
param is stripped by the transpilation process & given ctor
instead.
The result is the error TypeError: Right-hand side of 'instanceof' is not an object
import { elements } from 'domino/lib/htmlelts'
console.debug(elements) // { ctor: [Function: ctor] }
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Right-hand side of 'instanceof' is not an object - Bountysource
Webpack or Rollup transpilation error - TypeError: Right-hand side of 'instanceof' is not an object.
Read more >TypeError: invalid 'instanceof' operand 'x' - JavaScript | MDN
The instanceof operator expects the right-hand-side operands to be a constructor object, i.e. an object which has a prototype property and is ...
Read more >How to fix "TypeError: Right-hand side of 'instanceof' is not ...
The problem is that you have a circular dependency. The other file requires index , index requires Transaction , and Transaction requires ...
Read more >@babel/plugin-transform-instanceof | Yarn - Package Manager
This plugin transforms all the ES2015 'instanceof' methods. babel-plugin ... :eyeglasses: [Spec Compliance]; :rocket: [New Feature]; :bug: [Bug Fix] ...
Read more >TypeScript Deep Dive
TypeScript's Type System ... Type errors do not prevent JavaScript emit ... Now the awesome part: The inner function can access the variables...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
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
As the project seems to be sleeping at the moment, I published a build with this fix on npm https://www.npmjs.com/package/domino-ext. But I would like to see it applied here on the original.
This still appears to be an issue in release 2.1.6. The domino-ext fork works for me