ReferenceError: XMLHttpRequest is not defined when connecting with a token about remotestorage.js

[bdashore3]

Using node-fetch did not work due to type errors when setting the global variable (didn't want to deal with that headache), so I opted to use cross-fetch instead, which is a better library with type defs.

Here's the code for anyone else who stumbles upon this issue:

import 'cross-fetch/polyfill';

import RemoteStorage from 'remotestoragejs';

const remoteStorage = new RemoteStorage({ logging: true });
remoteStorage.access.claim('*', 'rw');

// Replace with your token/username
remoteStorage.connect('[email protected]', 'token');

[raucao]

It seems you're trying this from node.js or a similar non-browser environment? If so, you may need a polyfill library for either XMLHttpRequest or Fetch.

[bdashore3]

How would this be implemented in typescript? The XMLHttpRequest library doesn't have any type defs on npm, so I get a bunch of errors

Therefore, I can't do global.XMLHttpRequest = xmlHttpRequest

https://www.npmjs.com/package/xmlhttprequest

Here's my full typescript code

import RemoteStorage from 'remotestoragejs';

const remoteStorage = new RemoteStorage();
remoteStorage.access.claim('*', 'rw');

remoteStorage.connect('[email protected]', 'token');

[bdashore3]

Update: After some research, I was able to use isomorphic-fetch for the polyfill. Is there a simpler way to accomplish this, or did I do it right?

import 'isomorphic-fetch';

import RemoteStorage from 'remotestoragejs';

const remoteStorage = new RemoteStorage({ logging: true });
remoteStorage.access.claim('*', 'rw');

remoteStorage.connect('[email protected]', 'token');

[raucao]

Good question! We only moved to typescript with 2.0.0, which is why it's still officially a beta version and native TS usage might not be 100% there yet.

Could you try https://www.npmjs.com/package/node-fetch instead?

rs.js supports both fetch and the older xmlhttprequest. But the node-fetch library comes with TS definitions bundled by default.

[raucao]

Great! I created an issue to document this properly.