gilbsgilbs / babel-plugin-i18next-extract

Babel plugin that statically extracts i18next and react-i18next translation keys.
https://i18next-extract.netlify.com
MIT License
160 stars 37 forks source link

An in-range update of rollup is breaking the build 🚨 #135

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency rollup was updated from 1.32.0 to 1.32.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **gilbsgilbs.babel-plugin-i18next-extract (Run tests Run tests suite node13):** [1 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655) - βœ… **gilbsgilbs.babel-plugin-i18next-extract (Run tests Run tests suite node12):** [0 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655) - βœ… **gilbsgilbs.babel-plugin-i18next-extract (Run tests Run tests suite node10):** [0 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655) - ❌ **gilbsgilbs.babel-plugin-i18next-extract:** [1 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655) - βœ… **gilbsgilbs.babel-plugin-i18next-extract (Static checks Run ESLint):** [0 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655) - βœ… **gilbsgilbs.babel-plugin-i18next-extract (Static checks Run Yarn Audit):** [0 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655) - βœ… **gilbsgilbs.babel-plugin-i18next-extract (Static checks Run Typing Checks):** [0 errors / 0 warnings](https://dev.azure.com/gilbsgilbert/7092471e-19a9-41a2-8246-46803e7b5e4e/_build/results?buildId=655)

Release Notes for v1.32.1

2020-03-06

Bug Fixes

  • Handle default export detection for AMD and IIFE externals that do not have a prototype (#3420)
  • Handle missing whitespace when the else branch of an if-statement is simplified (#3421)
  • Mention the importing module when reporting errors for missing named exports (#3401)
  • Add code to warning for missing output.name of IIFE bundles (#3372)

Pull Requests

  • #3372: Add warning code for missing output.name of IIFE bundle that has export (@rail44)
  • #3401: Missing exports errors now print the importing module (@timiyay)
  • #3418: Structure lifecycle hooks, add links to build time hooks (@lukastaegert)
  • #3420: Update generated code of getInteropBlock() to work with null prototype objects (@jdalton)
  • #3421: Avoid invalid code when "else" branch is simplified (@lukastaegert)
Commits

The new version differs by 8 commits.

  • f458cbf 1.32.1
  • 8cbf216 Update changelog
  • 97b8c40 warn.code for missing output.name of IIFE bundle that has export (#3372)
  • eeda078 Update generated code of getInteropBlock() to work with null prototype objects (#3420)
  • 85c54ee Avoid invalid code when "else" branch is simplified (#3421)
  • 1e6284f Missing exports errors now print the importing module (#3401)
  • baf382a Fix internal documentation links
  • 6f0f62b Structure lifecycle hooks, add links to build time hooks (#3418)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

After pinning to 1.32.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.