Missing dependency on React prevents Webpack from importing about react-i18next HOT 9 CLOSED

nope...gave an answer there...not having react as dependency will not cause this.

from react-i18next.

I have the same problem :/

Uncaught Error: Cannot find module 'react'

ReactDOM.render(
  <I18nextProvider i18n={i18n}>
    <Provider store={store}>
      <Router history={browserHistory}>
        <Route path="/" component={App}>
          <IndexRoute component={Login} />
          <Route path="/home" component={Nav}>
            <Route path="/customers" component={CustomersList}>
              <Route path=":customerId" component={CustomersDetail} />
            </Route>
          </Route>
        </Route>
      </Router>
    </Provider>
  </I18nextProvider>,
  document.querySelector('.react-root')
);

from react-i18next.

http://stackoverflow.com/questions/35368799/react-i18n-redux-and-react-router-configuration

https://babeljs.io/repl/#?experimental=false&evaluate=true&loose=false&spec=false&code=%3Cdiv%20%2F%3E

from react-i18next.

I did'nt copy paste all my file. I already import the React module. All works, except when I use I18nextProvider.

from react-i18next.

hm...then i'm wondering...can't reproduce. we neither have this in our production applications nor in the example inside this repo...

would be glad if you could further investigate...

from react-i18next.

are you using this with meteor? if so i just got a interesting hint from @mjmasn here i18next/i18next#570 (comment)

from react-i18next.

I found the solution ! My fault :/
I used import { I18nextProvider } from 'react-i18next'; instead of import { I18nextProvider } from 'react-i18next/lib'; with my webpack config.

from react-i18next.

i see...hm. just thought about changing package.json main to point there...makes live more easy for the ones using a modern build chain - which hopefully are more then building some strange stuff using amd.

from react-i18next.

starting with v1.0.0 package.json will point to /lib/index.js

from react-i18next.