Can't access the JSDOM API #26
Comments
|
+1 |
|
This is an important issue, because |
Li0liQ
added a commit
to Li0liQ/jsdom-global
that referenced
this issue
Jul 17, 2017
Will allow to access jsdom API (rstacruz#26).
skomorokh
added a commit
to folio-org/stripes-connect
that referenced
this issue
Jul 27, 2017
I'd have preferred to leave this in place until I've finished building the replacement. Alas, use of window.alert() didn't play well with the test environment since jsdom-global doesn't expose enough of jsdom for me to override window.alert nor prevent its absence from cancelling the test. rstacruz/jsdom-global#26
|
I think this manual script from the Enzyme docs more-or-less deprecates this package and solves this issue. Quoting for convenience: /* setup.js */
const { JSDOM } = require('jsdom');
const jsdom = new JSDOM('<!doctype html><html><body></body></html>');
const { window } = jsdom;
function copyProps(src, target) {
Object.defineProperties(target, {
...Object.getOwnPropertyDescriptors(src),
...Object.getOwnPropertyDescriptors(target),
});
}
global.window = window;
global.document = window.document;
global.navigator = {
userAgent: 'node.js',
};
global.requestAnimationFrame = function (callback) {
return setTimeout(callback, 0);
};
global.cancelAnimationFrame = function (id) {
clearTimeout(id);
};
copyProps(window, global);You can export the instance, make it global, whatever works for your use case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of version 3, there's no way to access the JSDOM api (here) directly. Some functions such as
reconfigureare important.How do you think we can expose a reference to it? Please guide me and I'll be happy to make a PR.
Thanks!
The text was updated successfully, but these errors were encountered: