Cannot find module 'babel/register'

[ericclemmons]

Cannot find module 'babel/register'

[ericclemmons]

@bbnnt Within those example directories did you run npm install & npm start?

[jasonphillips]

A clarification on this one: I ran into it as well on a clean installation of the example folder.

It appears that the issue is simply that src/server.js calls require(babel/register), while the package.json for the example installs babel-core instead of babel.

It will function nonetheless if you have already run npm install in the root of the react-resolver project, because there babel is installed and the require statement from the example will find it in that parent folder.

The fix to make the example work independently as designed is simply to require babel-core/register instead of babel/register in server.js, since that is the module it installs. This fix should avert the issue for others who run into this simple roadblock by running the example on its own.

[benbonnet]

sure did; won't say I'm expert in react and the ecosystem, but I've understood how webpack works, how to use package.json, etc… the basic architecture of those tools.

But never seen any examples using this piping thing, I was expecting to be lucky if this one sounded obvious for you

[ericclemmons]

@bbnnt Sorry, I didn't mean to make it seem like you didn't know. Someone brought up the docs for the examples once before & I was hoping it was the same here.

Reason being, I just did a git clean -fdx. && npm start within the example & had it running:

Although now I fear there's a regression with HistoryLocation :(

[benbonnet]

No problem, I was just in hope to find out and understand things better hacking with your examples.

Damn it, being a "server-side-dev", I'm was looking for a clean way to get into isomorphism. so far I was pretty disapointed with what exists in the ecosystem; but have to say your tool is perfect (doing data call from within the components, I just don't understand why it is not a main concern in react and why isomorphism got so big without actually providing a solid pattern for calling data server-side before rendering)

Tried out your command, still got the same problem.

Could it come from my node version maybe ? Mine is v0.12.6.

I might figure it out anyway. Thanks a lot for your time!

[ericclemmons]

That's really bizarre! Do you have babel installed globally? npm run commands automatically path node_modules/.bin from the local install, but globals still take precedent.

[benbonnet]

Too bad for the examples, but I gave it up; wasn't a big deal
In any cases I managed to use your project as intended ! #76 seems more important in any cases

[ericclemmons]

Sorry it didn't work out. Truthfully, it sounds more like the npm install messed up on your machine.

[ericclemmons]

Ah, and you answered it here. Thanks :)

[benbonnet]

well not sure if it was updated or not, but it does now work !
thx

[ericclemmons]

Yay, thanks @jasonphillips!