chore(deps): update babel monorepo (major) - autoclosed

Closed renovate-bot requested to merge renovate/major-babel-monorepo into develop

This MR contains the following updates:

Package Type Update Change
babel-eslint devDependencies major 8.2.6 -> 10.1.0
babel-loader devDependencies major 8.2.5 -> 9.1.0

Release Notes

babel/babel-eslint

v10.1.0

Compare Source

v10.0.3

Compare Source

Fixes https://github.com/babel/babel-eslint/issues/791, also https://github.com/eslint/eslint/issues/12117

Some context: https://github.com/babel/babel-eslint/pull/793#issuecomment-524435971

We ended up going with @​JLHwung's MR https://github.com/babel/babel-eslint/pull/794 which uses ESLint's deps instead of going with peerDeps since it really depends on the version being used and we don't want users to have to install it directly on their own.

babel-eslint is patching patches of the dependencies of ESLint itself so these kinds of issues have happened in the past. We'll need to look into figuring out how to have a more solid way of modifying behavior instead of this monkeypatching type of thing for future releases.

v10.0.2

Compare Source

Fixes https://github.com/babel/babel-eslint/issues/772

v10.0.1

Compare Source

v10.0.1

The TypeAlias "conversion" to a function has issues. Sounds like we need to rethink the change, most likely we can just actually change the scoping rather than hardcode an AST change.

v10.0.0

Compare Source

v10.0.0

Small breaking change: add a peerDependency starting from the ESLint version that added a parser feature that we were monkeypatching before (and drop that code). If already using ESLint 5 shouldn't be any different.

/* @​flow */
type Node<T> = { head: T; tail: Node<T> }

// or 

type File = {chunks: Array<Chunk>}
type Chunk = {file: File}

v9.0.0

Compare Source

v9.0.0

We've released v7: https://twitter.com/left_pad/status/1034204330352500736, so this just updates babel-eslint to use those versions internally. That in itself doesn't break anything but:

  • Babel now supports the new decorators proposal by default, so we need to switch between the new and the old proposal. This is a breaking change.

To enable the legacy decorators proposal users should add a specific parser option:

{
  parserOptions: {
    ecmaFeatures: {
      legacyDecorators: true
    }
  }
}
  • Babel removed the support for Node 4 , so I propagated that here.
babel/babel-loader

v9.1.0

Compare Source

New features

Full Changelog: https://github.com/babel/babel-loader/compare/v9.0.1...v9.1.0

v9.0.1

Compare Source

Bug Fixes

Full Changelog: https://github.com/babel/babel-loader/compare/v9.0.0...v9.0.1

v9.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/babel/babel-loader/compare/v8.2.5...v9.0.0

v8.3.0

Compare Source

New features

Full Changelog: https://github.com/babel/babel-loader/compare/v8.2.5...v8.3.0


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.


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

This MR has been generated by Renovate Bot.

Edited by renovate-bot

Merge request reports