11.17.3

11.17.2

11.17.1

11.17.0

11.16.11

11.16.10

11.16.9

11.16.8

11.16.7

11.16.6

11.16.5

11.16.4

11.16.3

11.16.2

11.16.1

11.16.0

11.15.7

11.15.6

11.15.5

11.15.4

11.15.3

11.15.2

11.15.1

11.15.0

11.14.3

11.14.2

11.14.1

11.14.0

11.13.0

11.12.0

11.11.4

11.11.3

11.11.2

11.11.1

11.11.0

11.10.0

11.9.0

11.8.15

11.8.14

11.8.13

11.8.12

11.8.11

11.8.10

11.8.9

11.8.8

11.8.7

11.8.6

11.8.5

11.8.4

11.8.3

11.8.2

11.8.1

11.8.0

11.7.4

11.7.3

11.7.2

11.7.1

11.7.0

11.6.0

11.5.1

11.5.0

11.4.0

11.3.5

11.3.4

11.3.3

11.3.2

11.3.1

11.3.0

11.2.7

11.2.6

11.2.5

11.2.4

11.2.3

11.2.2

11.2.1

11.2.0

11.1.0

11.0.1

11.0.0

10.13.2

10.13.1

10.13.0

10.12.5

10.12.4

10.12.3

10.12.2

10.12.1

10.12.0

10.11.5

10.11.4

10.11.3

10.11.2

10.11.1

10.11.0

10.10.0

10.9.1

10.9.0

10.8.1

10.8.0

10.7.0

10.6.2

10.6.1

10.6.0

10.5.3

10.5.2

10.5.1

10.5.0

10.4.2

10.4.1

10.4.0

10.3.1

10.3.0

10.2.1

10.2.0

10.1.2

10.1.1

10.1.0

10.0.5

10.0.4

10.0.3

10.0.2

10.0.1

10.0.0

10.0.0-alpha.3

10.0.0-alpha.2

10.0.0-alpha.1

9.0.10

9.0.9

9.0.8

9.0.7

9.0.6

9.0.5

9.0.4

9.0.3

9.0.2

9.0.1

9.0.0

BREAKING

Using react >= 16.3.0 will be save - in other cases you will need to polyfill react.createContext yourself!!

8.4.0

8.3.9

8.3.8

8.3.7

8.3.6

8.3.5

8.3.4

8.3.3

8.3.2

8.3.1

8.3.0

8.2.0

8.1.2

8.1.1

8.1.0

8.0.8

8.0.7

8.0.6

8.0.5

8.0.4

8.0.3

8.0.2

8.0.1

8.0.0

'Hello <1><0>{{name}}</0></1>, you have <3>{{count}}</3> message. Open <5>hear</5>.'

can be written as:

'Hello <1>{{name}}</1>, you have {{count}} message. Open <5>hear</5>.'

=> there is no need to add <0>...</0> around interpolated values anylonger => your old files having those extra pseudo tags will still work without needing to change them

Using react’s new context api

should be non breaking in most cases, with following exceptions:

still we prefer to increase this to a major version as beside the described egde cases there might be other effects we not have covered with our tests

7.13.0

7.12.0

7.11.1

7.11.0

7.10.1

7.10.0

7.9.1

7.9.0

7.8.1

7.8.0

7.7.0

7.6.1

7.6.0

7.5.1

7.5.0

7.4.0

7.3.6

7.3.5

7.3.4

7.3.3

7.3.2

7.3.1

7.3.0

7.2.0

7.1.1

7.1.0

7.0.2

7.0.1

7.0.0

Starting with v7.0.0 Trans component per default won’t add a parent div around content passed as children. It will just return it’s children.

You still got the option to set a parent if you prefer content being wrapped.

If you prefer wrapping for all your Trans components (or for backwards compatibility) you can set option react.defaultTransParent to an element on i18next init.

6.2.0

6.1.0

6.0.6

6.0.5

6.0.4

6.0.3

6.0.2

6.0.1

6.0.0

5.4.1

5.4.0

5.3.0

5.2.0

5.1.0

import translate from 'react-i18next';
import i18n from './i18n';

translate.setI18n(i18n);

5.0.0

i18next.init({
  // ... other options
  react: {
    wait: false,
    withRef: false,
    bindI18n: 'languageChanged loaded',
    bindStore: 'added removed',
    nsMode: 'default'
  }
});
import translate from 'react-i18next';

translate.setDefaults({
  wait: false,
  withRef: false,
  bindI18n: 'languageChanged loaded',
  bindStore: 'added removed',
  nsMode: 'default',
  translateFuncName: 't'
});

4.8.0

4.7.0

4.6.4

4.6.3

4.6.2

4.6.1

4.6.0

4.5.0

4.4.0

4.3.0

4.2.0

4.1.2

4.1.1

4.1.0

4.0.0

3.1.2

3.1.1

3.1.0

3.0.0

2.2.3

2.2.1

2.2.0

2.1.0

2.0.0

1.11.0

1.10.1

1.10.0

1.9.0

1.8.0

1.7.0

1.6.3

1.6.2

1.6.1

1.6.0

1.5.3

1.5.2

1.5.1

1.5.0

1.4.2

1.4.1

1.4.0

1.3.0

1.2.2

1.2.0

1.1.0

1.0.1

1.0.0