Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade i18n from 0.5.0 to 0.13.4 #2

Open
wants to merge 1 commit into
base: Java
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade i18n from 0.5.0 to 0.13.4.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 20 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2021-12-29.
Release notes
Package name: i18n
  • 0.13.4 - 2021-12-29

    Fixed

    • upgrade all dev dependencies without breaking changes
    • upgrade all dependencies without breaking changes

    see aa60ac7, 3139881 and 4e6963f for details

    Added

    • test directory traversal (#486)
  • 0.13.3 - 2021-05-08

    Fixed

  • 0.13.2 - 2020-08-21

    Fixed

    • moved devDeps from dependencies to devDependencies #446
    • removed unused packages from all dependencies
  • 0.13.1 - 2020-08-20

    Fixed

    • npx npm-force-resolutions failed #445

    Details

    A preinstall script was added to force resolving specific versions of lodash and ajv. Those are sub-dependencies of zombie and its packages. Zombie is devDependency of i18n. But zombie still refers to older versions reported to vulnerable - so I decided to force fixed versions.

    Of course that preinstall should count on any npm install i18n, it's renamed to force-resolutions so I can still resolve audit issues in dev while also supporting clean installs.

    "scripts": {
      "preinstall": "npx npm-force-resolutions"
    }

    now reads as

    "scripts": {
      "force-resolutions": "npx npm-force-resolutions"
    }

    And doesn't get triggered by npm install.

  • 0.13.0 - 2020-08-20

    Added

    • new option retryInDefaultLocale as proposed by PR #206
    • new option header as proposed by PRs #390 and #407
    • pre-commit hooks to ensure code-style (even on contributions)

    Fixed

    • typos in README

    Changed

    • tooling: eslint with standard.js & prettier presets replaces jshint
  • 0.12.0 - 2020-08-16

    Added

    • backward compatible default to singleton with const i18n = require('i18n')
    • create an instance of i18n by const i18n = new I18n()

    Example:

    /**
    * require I18n with capital I as constructor
    */
    const { I18n } = require("i18n");

/**
* create a new instance with it's configuration
*/
const i18n = new I18n({
locales:['en', 'de'],
directory: __dirname + '/locales'
});


  • 0.11.1 - 2020-08-04

    Fixed

    • dependabot bumbed minimist

    Minimist is a sub-dependency of mocha and messageformat:

    $ npm ls minimist
    [email protected] 
    ├─┬ [email protected]
    │ └─┬ [email protected]
    │   └── [email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        └── [email protected]  deduped
  • 0.11.0 - 2020-08-03

    Added

    • Fallbacks can use wildcards (#361) by PR #362
    • New mustache options to tweak tags and/or disable mustache parsing (#436)

    Fixed

    • Mitigated Uncaught Exception on malformed query param (#356, #422) by PR #442
    • Use of single pipe character should not be interpreted as range (#274, #388). Fixed by PR #435
  • 0.10.0 - 2020-05-24

    Thanks to @ einfallstoll i18n got much more developer friendly by adding two extra configuration options for working with translation files catalogs.

    Added

    • Adds support for priming i18n with static catalogs (PR #432)
    • Adds support for custom callback/hook on missing translations thru missingKeyFn option ℗ #433 )

    Examples

    staticCatalog

    Instead of letting i18n load translations from a given directory you may now pass your js object right on configuration, ie:

    // DEMO: quick add yaml support on your own
    const yaml = require('js-yaml');
    const fs = require('fs');

    // configure and load translations from different locations
    i18n.configure({
    staticCatalog: {
    de: require('../../locales/de.json'),
    en: require('../../locales/wired-en-filename.js'),
    fr: yaml.safeLoad(fs.readFileSync('../../locales/yaml/fr/server.yml', 'utf8'));
    },
    defaultLocale: 'de'
    })

    This opens up for a ton of possible ways to handle translations in your very own desired way. But be warned: "Great power comes with great responsibility".

    missingKeyFn

    Want to get a warning on missing translations? Add missing translations with an indicator? Or even want to try an external service (like deepl.com) to provide an automated translated proposal of a missing phrase?

    i18n.configure({
      missingKeyFn(locale, value) {
        console.warn(`missing translation of "${value}" in [${locale}]!`)
        return `${value}-[${locale}]`;
      },
      defaultLocale: 'de'
    })
  • 0.9.1 - 2020-05-03

    Fixed

    • Catch race condition in parallel fs tasks (PR #431)
    • Update packages, remove unused url
  • 0.9.0 - 2020-04-17
  • 0.8.6 - 2020-03-17
  • 0.8.5 - 2020-01-26
  • 0.8.4 - 2019-10-24
  • 0.8.3 - 2016-06-21
  • 0.8.2 - 2016-04-20
  • 0.8.1 - 2016-03-03
  • 0.8.0 - 2016-02-28
  • 0.7.0 - 2016-02-15
  • 0.6.0 - 2016-01-31
  • 0.5.0 - 2014-06-14
  • from i18n GitHub release notes

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

    For more information:

    🧐 View latest project report

    🛠 Adjust upgrade PR settings

    🔕 Ignore this dependency or unsubscribe from future upgrade PRs

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    1 participant