Console error when using ?_escaped_fragment_= about spiderable HOT 3 CLOSED

Actually when hosting on the server I get the following error on the browser window itself when including the escaped fragment:

ReferenceError: Can't find variable: Stripe

http://localhost:8080/565a9e95138619c4ffb527bd07b1d6785d06516c.js:326
http://localhost:8080/565a9e95138619c4ffb527bd07b1d6785d06516c.js:3
http://localhost:8080/565a9e95138619c4ffb527bd07b1d6785d06516c.js:3

from spiderable.

the stripe error should be unrelated. Perhaps that's a different issue? In any case, doesn't sound like it's working (or configured) properly - you shouldn't see any errors. this version of spiderable was made specifically to deal with docker (or a proxy) where spiderable needs to work behind a defined port. you might try passing --port xxxx to the meteor statement. Unless you are having specific problems with proxies, docker,etc I'd probably suggest not using this package. regular meteor:spiderable should work locally in most all cases.

from spiderable.

Got it. I was having errors occur on Modulus, so I gave it a try, but it seems to be resolved with an alternative phantomJS package. Not sure why the stripe error. It went away when switching back to the regular spiderable package.

from spiderable.