s2/vanillajs-seed
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

update modules

Browse Source
This commit is contained in:
s2
2020-06-08 08:50:28 +02:00
parent ae4aaf2668
commit 27635904a6
477 changed files with 20385 additions and 35036 deletions
Download Patch File Download Diff File Expand all files Collapse all files

193
node_modules/i18next/CHANGELOG.md generated vendored
View File

@@ -1,3 +1,196 @@
### 19.4.5
- Add store events to typings [1451](https://github.com/i18next/i18next/pull/1451)
### 19.4.4
- typescript: Allow passing retry boolean to `ReadCallback` [1439](https://github.com/i18next/i18next/pull/1439)
### 19.4.3
- fix regression introduced in "support formatting in nesting" [1419](https://github.com/i18next/i18next/pull/1419)
### 19.4.2
- fix for deno [1428](https://github.com/i18next/i18next/pull/1428)
### 19.4.1
- add getLanguagePartFromCode as in language fallback resolution [1424](https://github.com/i18next/i18next/pull/1424)
### 19.4.0
- support formatting in nesting [1419](https://github.com/i18next/i18next/pull/1419)
### 19.3.4
- fix cloning of service.utils binding to clone [1415](https://github.com/i18next/i18next/pull/1415)
### 19.3.3
- backendConnector extend initial retry from 250 to 350
### 19.3.2
- fix the nested string options parsing introduced in v19.2.0 which broke having multiple options
### 19.3.1
- typescript: add `options.interpolation.nestingOptionsSeparator`
### 19.3.0
- Double fix for 1395 issue [1399](https://github.com/i18next/i18next/pull/1399)
- adds `options.interpolation.nestingOptionsSeparator: ','` to specify that separator
### 19.2.0
- Add ability to use commas in nested keys [1398](https://github.com/i18next/i18next/pull/1398)
### 19.1.0
- explict warning when no languageDetector is used and no lng is defined [1381](https://github.com/i18next/i18next/pull/1381)
- Add option to always format interpolated values [1385](https://github.com/i18next/i18next/pull/1385)
- pass all options to format function [992#issuecomment-577797162](https://github.com/i18next/i18next/issues/992#issuecomment-577797162)
### 19.0.3
- fixes retry interval in backend connector [1378](https://github.com/i18next/i18next/issues/1378)
### 19.0.2
- typescript: Type ResourceStore [1366](https://github.com/i18next/i18next/pull/1366)
### 19.0.1
- ignore non valid keys in saveMissing [1359](https://github.com/i18next/i18next/pull/1359)
### 19.0.0
- typescript: Typescript use `export default` for esm-first approach [1352](https://github.com/i18next/i18next/pull/1352)
### 18.0.1
- check loadedNamespace only once per lng-ns inside using `t` for better performance
### 18.0.0
- When calling `i18next.changeLanguage()` both `i18next.language` and `i18next.languages` will be set to the new language after calling `loadResources` -> means when accessing `t` function meanwhile you will get still the translations for the previous language instead of the fallback.
- **When is this breaking?** this does not break any current test - but if you depend on accessing i18next.language or i18next.dir during language change and expect the new language this will break your app.
- Reasoning: In react-i18next we get in a not ready state for loaded translations while we would prefer just waiting for the new language ready and trigger a rerender then - also a triggered rerender outside of the bound events would end in Suspense...
- How can I get the language i18next will be set to? `i18next.isLanguageChangingTo` is set to the language called
### 17.3.1
- typescript: Add missing `cleanCode` option to TypeScript def [1344](https://github.com/i18next/i18next/pull/1344)
### 17.3.0
- pass used language & namespace to postprocessor [1341](https://github.com/i18next/i18next/pull/1341)
### 17.2.0
- Support using ImmutableJS Records as the data model in interpolation [1339](https://github.com/i18next/i18next/pull/1339)
### 17.1.0
DX improvements:
- warning if accessing t before i18next was initialized or namespace loaded
- warning and cancelling save if saveMissing key before i18next was initialized or namespace loaded
Both are a clear sign you render your app / call t to early not waiting for the callbacks or Promise.resolve on i18next.init, i18next.loadNamespace or i18next.changeLanguage.
### 17.0.18
- Improve performance of EventEmitter.off [1333](https://github.com/i18next/i18next/pull/1333)
### 17.0.17
- fixes: missing nested key fails if no nested value found and defaultValue contains interpolation -> results in endless loop [1332](https://github.com/i18next/i18next/issues/1332)
### 17.0.16
- typescript: fix incorrect callback type for backend module read callback [1322](https://github.com/i18next/i18next/pull/1322)
- typescript: add getDataByLanguage into index.d.ts [1326](https://github.com/i18next/i18next/pull/1326)
### 17.0.15
- Fixed default value as string in IE [1325](https://github.com/i18next/i18next/pull/1325)
### 17.0.14
- typescript: Allow TFunction to receive 1-3 parameters [1317](https://github.com/i18next/i18next/pull/1317)
### 17.0.13
- fixes: Interpolation defaultVariables not recognized on t() [1314](https://github.com/i18next/i18next/issues/1314)
### 17.0.12
- remove unused Interpolator#init reset param (only used internally) [1313](https://github.com/i18next/i18next/pull/1313)
- Cope with null interpolation (unescaped case) [1310](https://github.com/i18next/i18next/pull/1310)
### 17.0.11
- fix issue with unset value in interpolation throwing exception
- typescript: Allow augmentation of TFunction to be able to add overloads [1308](https://github.com/i18next/i18next/pull/1308)
### 17.0.10
- Update Interpolator.js to use regexSafe for unescaped interpolation [1307](https://github.com/i18next/i18next/pull/1307)
### 17.0.9
- typescript: use() should accept a class or object [1301](https://github.com/i18next/i18next/pull/1301)
### 17.0.8
- typescript: Correct `use(module)` types [1296](https://github.com/i18next/i18next/pull/1296)
### 17.0.7
- typescript: Typescript imports [1291](https://github.com/i18next/i18next/pull/1291)
- Disabled default returnedObjectHandler [1288](https://github.com/i18next/i18next/pull/1288)
### 17.0.6
- support montenegrien "crn" plurals
### 17.0.4
- typescript: ResourceKey type should allow top level string value [1267](https://github.com/i18next/i18next/pull/1267)
### 17.0.3
- don't do named exports for umd
### 17.0.2
- typescript: Allow null as TResult [1263](https://github.com/i18next/i18next/pull/1263)
- bring back ./i18next.js and ./i18next.min.js -> used by wildcard unpkg users...<= bad idea doing so
- main export in package.json points to cjs dist
### 17.0.1
- adapt ./index.js to 17.0.0 export
### 17.0.0
- removes checking in build files (umd) into source code - for CDN usage use: [https://unpkg.com/i18next@16.0.0/dist/umd/i18next.js](https://unpkg.com/i18next@16.0.0/dist/umd/i18next.js)
- removes named exports in main file - avoids issues in mixed exports makes usage better in commonjs scenarios (node.js) - no strange `const i18next = require('i18next').default;`
- **impact** you can't no longer `import { changeLanguage } from 'i18next'; changeLanguage('de');` you will have to `import i18next from 'i18next'; i18next.changeLanguage('de');`
- **note** if can create a own file providing the named bound functions and use that instead, sample: [https://github.com/i18next/i18next/blob/v15.0.0/src/index.js#L5](https://github.com/i18next/i18next/blob/v15.0.0/src/index.js#L5)
### 16.0.0
- removes deprecated jsnext:main from package.json
- Bundle all entry points with rollup [1256](https://github.com/i18next/i18next/pull/1256)
- **note:** dist/es -> dist/esm, dist/commonjs -> dist/cjs (individual files -> one bundled file)
### 15.1.3
- typescript: Fix type error when init with locize plugin options [1248](https://github.com/i18next/i18next/pull/1248)