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.

Sign up for GitHub

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

Jump to bottom

Update dependency babel-preset-env to v1.7.0 #11

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

Update dependency babel-preset-env to v1.7.0 #11

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 23, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
babel-preset-env (source) 1.1.8 -> 1.7.0 age adoption passing confidence

Release Notes

babel/babel-preset-env (babel-preset-env)

v1.7.0

Compare Source

v1.6.1

Compare Source

🐛 Bug Fix

ES2015 destructuring is not fully supported in Edge 15 and the polyfill required again. es6.math.imul is supported on Android as of version 4.4

Functions such as Object.keys, Object.freeze, ... do already exist in ES5, but their behaviour changed in ES2015. babel-preset-env with builtIns: true now adds the core-js polyfills for this methods if the browser only supports the ES5 variant of the method (like IE11 for example)

v1.6.0

Compare Source

🚀 New Feature

We updated our mappings to support native trailing function commas and string paddings in Node.js 8+.

🐛 Bug Fix

We added support for using browserslist's chromeandroid in targets.

📝 Documentation

Thanks to @​graingert and @​pfiaux for pointing out some needed updates to the uglify-js-related docs.

v1.5.2

Compare Source

🐛 Bug Fix

browser targets should be overridden by explicit targets, and we inadvertently broke this when we landed string version support.

v1.5.1

Compare Source

🐛 Bug Fix

v1.5.0

Compare Source

🚀 New Feature

We were originally waiting on 2.x for a breaking change, but since node v7.10
and other targets are causing some pain, we decided to land a backwards
compatible version.

🏠 Internal

v1.4.0

Compare Source

🚀 New Feature

Added an option to enable more spec compliant, but potentially slower, transformations for any plugins in this preset that support them.

We updated our mappings so that you can get native support for async/await and other goodies when targeting Edge 15!

🐛 Bug Fix

Fixed a bug that was ignoring Android targets in browserslist queries (for example: "Android >= 4").

📝 Documentation
🏠 Internal

v1.3.3

Compare Source

🐛 Bug Fix

Adding electron as a target was an inadvertent breaking change as it no longer
allowed string versions. We added an exception for now, even though it is
inconsistent with other versions. Just as a note, the upcoming version 2.x will
allow both number and string versions.

We now force the const-es2015-check plugin to run first (so that it can
correctly report issues before they get transpiled away).

🚀 New Feature

The include and exclude options now allow both prefixed (babel-plugin-transform-es2015-spread)
and prefix-less (transform-es2015-spread) plugin names.

📝 Documentation
🏠 Internal

v1.3.2

Compare Source

  • Fixed an issue with a broken publish

v1.3.1

Compare Source

  • Fixed a regression with missing files due to .npmignore.

v1.3.0

Compare Source

🐛 Bug Fix

We now properly check for Symbol.species support in ArrayBuffer and include the
polyfill if necessary. This should, as a side effect, fix ArrayBuffer-related
errors on IE9.

💅 Polish

We've simplified things by adding electron as a target instead of doing a bunch of
things at runtime. Electron targets should now also be displayed in the debug output.

If you are targeting the node environment exclusively, the always-included web polyfills
(like dom.iterable, and a few others) will now no longer be included.

📝 Documentation
🏠 Internal

v1.2.2

Compare Source

🐛 Bug Fix

When parsing plugin data, we weren't properly handling browser families. This caused
transform-es2015-block-scoping and other plugins to be incorrectly added for Edge >= 12.
(s/o to @​mgol for the the report and review!)

Fixes an issue where some TypedArray features were not being polyfilled properly. (s/o to @​alippai for the report!)

📝 Documentation
🏠 Internal

v1.2.1

Compare Source

🐛 Bug Fix

Our plugin data was missing a mapping for the transform-duplicate-keys plugin which caused it to never be included. (s/o to @​Timer for the report!)

📝 Documentation

v1.2.0

Compare Source

🚀 New Feature

Support for uglify as a target is now available! This will enable all plugins and, as a result, fully compiles your code to ES5. Note, that useBuiltIns will work as before, and only the polyfills that your other target(s) need will be included.

{
  "presets": [
    ["env", {
      "targets": {
        "chrome": 55,
        "uglify": true
      },
      "useBuiltIns": true,
      "modules": false
    }]
  ]
}
🐛 Bug Fix

Fixes a number of bugs that caused some incorrect and/or missing environment data when parsing compat-table.

v1.1.11

Compare Source

This release primarily upgrades compat-table, which adds support for async on Node 7.6!

🐛 Bug Fix
📝 Documentation
🏠 Internal

v1.1.10

Compare Source

🐛 Bug Fix

v1.1.9

Compare Source

🐛 Bug Fix

Since we've (mostly @​yavorsky) have fixed a number of bugs recently with the debug option output, we added the ability to assert stdout matches what we expect. Read the updated CONTRIBUTING.md for more info.

This fixes a bug in the debug output where incorrect target(s) were being displayed for why a particular plugin/preset was being included.

Given targets:

{
  "firefox": 52,
  "node": 7.4
}

Before:

Using plugins:
  transform-es2015-destructuring {"node":6.5}
  transform-es2015-for-of {"node":6.5}
  transform-es2015-function-name {"node":6.5}
  transform-es2015-literals {"node":4}
  transform-exponentiation-operator {"firefox":52}
  syntax-trailing-function-commas {"firefox":52}

After:

Using plugins:
  transform-es2015-destructuring {"firefox":52}
  transform-es2015-for-of {"firefox":52}
  transform-es2015-function-name {"firefox":52}
  transform-es2015-literals {"firefox":52}
  transform-exponentiation-operator {"node":7.4}
  syntax-trailing-function-commas {"node":7.4}
📝 Documentation
🏠 Internal

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented May 23, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
error Can't add "websocket": invalid package version undefined.

@renovate renovate bot force-pushed the renovate/babel-preset-env-1.x-lockfile branch from 7bfc572 to 000fe6e Compare June 22, 2023 09:50
@renovate renovate bot force-pushed the renovate/babel-preset-env-1.x-lockfile branch from 000fe6e to 6fe2d58 Compare June 22, 2023 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants