Closed AdamBrodzinski closed 9 years ago
Frankly, I am quite not sure where this is coming from.
On 2015 ජූනි 29, සඳුදා at ප.ව. 8.31 Adam Brodzinski < notifications@github.com> wrote:
I'm not sure if this is a meteorhacks:npm issue but the source of the problem seems to be that React-Router expects modules to use module.exports (based on previous issues). Have you ran into this problem before?
TypeError: Object #
I also have a test repo here if you're interested:
https://github.com/AdamBrodzinski/meteor-react-ssr-spike
If I call renderToString on Home all is fine, but if I call it on Router it gets throws.
— Reply to this email directly or view it on GitHub https://github.com/meteorhacks/npm/issues/88.
Oh ok, thanks for the quick reply! I wasn't sure if this was a common thing. Look like it's not :frowning: . I'll keep digging. Feel free to close this if it's not in scope with the npm package.
I think we can close it. Anyway, if you find the issue try to put it here too. May be it'll be helpful for someone else.
Yep will do. Closing.
Great.
On Mon, Jun 29, 2015 at 8:40 PM Adam Brodzinski notifications@github.com wrote:
Closed #88 https://github.com/meteorhacks/npm/issues/88.
— Reply to this email directly or view it on GitHub https://github.com/meteorhacks/npm/issues/88#event-343128734.
I don't know where this is coming from but I'm running into it as well!
@john-osullivan one of your components is most likely undefined. This is really common in React Native when I import the wrong path or forget to export a module.
I'm not sure if this is a
meteorhacks:npm
issue but the source of the problem seems to be that React-Router expects modules to use module.exports (based on previous issues). Have you ran into this problem before?I also have a test repo here if you're interested:
https://github.com/AdamBrodzinski/meteor-react-ssr-spike
If I call
renderToString
onHome
all is fine, but if I call it on Router it gets throws.