Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of core-js is breaking the build 🚨

The devDependency core-js was updated from `3.5.0` to `3.6.0`.

🚨 View failing branch.

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

core-js 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for 3.6.0 - 2019.12.19

Added support of sticky (y) RegExp flag, #372, #732, #492, thanks @cvle and @nicolo-ribaudo
Added RegExp#test delegation to RegExp#exec, #732, thanks @cvle
Fixed some cases of Object.create(null) in IE8-, #727, #728, thanks @aleen42
Allowed object of minimum environment versions as core-js-compat and core-js-builder targets argument
Allowed corresponding to Babel targets.esmodules, targets.browsers, targets.node options in core-js-compat and core-js-builder
Engines in compat data and results of targets parsing sorted alphabetically
Fixed features/instance/match-all entry compat data
Fixed Array.prototype[@@unscopables] descriptor (was writable)
Added Samsung Internet 11 compat data mapping

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Media support

An in-range update of core-js is breaking the build 🚨

The devDependency core-js was updated from `3.4.4` to `3.4.5`.

🚨 View failing branch.

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

core-js 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for 3.4.5 - 2019.11.28

Detect incorrect order of operations in Object.assign, MS Edge bug
Detect usage of ToLength in Array#{ filter, map }, FF48-49 and MS Edge 14- issues
Detect incorrect MS Edge 17-18 Reflect.set which allows setting the property to object with non-writable property on the prototype
Fixed inspectSource helper with multiple core-js copies and some related features like some edge cases of Promise feature detection

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Update Node.js to v17

Abstracted transport layer

Is your feature request related to a problem? Please describe.
This library is tied to axios as the HTTP transport layer. We believe this library can be more flexible if it allows end users to implement their own transport layer - with axios as the default fallback for backwards compatibility.

Describe the solution you'd like
A simple abstracted transport layer e.g. (pseudo code)

Fetch

class FetchTransport {
  /**
   * Transport constructor.
   */
  constructor() {
    // Set up predefined resources methods.
    ["post", "get", "put", "patch", "delete"].forEach(verb => {
      this[verb] = (url, data, config) => this._request(verb, url, data, config);
    });
  }

  _request(verb, url, data, config) {
    const params = {
      method: verb.toUpperCase(),
      headers: {
        "Content-Type": "application/json",
        "Accept": "application/json"
      },
      body: JSON.stringify(data)
    };
    const response = fetch(url, params);
    return response.json();
  }
}

Axios

class AxiosTransport {
  /**
   * Transport constructor.
   */
  constructor() {
    this.axios = this._createAxiosClient();
    // Set up predefined resources methods.
    ["post", "get", "put", "patch", "delete"].forEach(verb => {
      this[verb] = (url, data, config) => this.axios[verb](url, data, config);
    });
  }

  /**
   * Create axios client.
   *
   * @return {Axios}
   */
  _createAxiosClient() {
    const auth = Object.assign({}, defaultOptions.auth, this.options.auth);
    const options = deepExtend({}, this.options.axios, {
      auth: auth.username.length || auth.password.length ? auth : null,
      baseURL: this._createBaseUrl(),
      headers: this.options.headers,
    });

    return axios.create(options);
  }  
}

Describe alternatives you've considered
None

Additional context
This is useful as many enduser apps would already be using their own library; superagent, axios, fetch etc.. and loading another library has unnecessary overheads and does not allow interoperability.

How would we swap them out without loading them? No idea may need a small breaking change to the library so the user npm install yllet yllet-fetch or npm install yllet yllet-axios then initialises the library as follows

import Client from 'yllet';
import AxiosTransport from 'yllet-axios';

const client = new Client({
  endpoint: 'https://demo.wp-api.org/wp-json/',
  transport: AxiosTransport 
});

An in-range update of core-js is breaking the build 🚨

The devDependency core-js was updated from `3.4.3` to `3.4.4`.

🚨 View failing branch.

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

core-js 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for 3.4.4 - 2019.11.27

Added feature detection for Safari non-generic Promise#finally bug (critical for core-js-pure)
Fixed missed esnext.string.code-points in core-js/features/string entry point
Updated Iterator proposal feature detection for the case of non-standard Iterator in FF44-

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

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

The devDependency rollup was updated from `1.27.5` to `1.27.6`.

🚨 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for v1.27.6

2019-11-30

Bug Fixes

Use "auto" export mode by default for all modules when preserving modules (#3265)
Observe "output.exports" when preserving modules and warn for mixed exports if necessary (#3265)

Pull Requests

#3265: Use export mode "auto" by default when preserving modules (@lukastaegert)

Commits

The new version differs by 3 commits.

5a01f05 1.27.6
fe0fced Update changelog
bdd1e03 Use export mode "auto" by default when preserving modules (#3265)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from `4.41.3` to `4.41.4`.

🚨 View failing branch.

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

webpack 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for v4.41.4

Bugfixes

fix case where __webpack_require__.e is not a function when using module concatenation
fix incorrect imported module when using sideEffects in a certain constellation of export names

Performance

lazy-require Webassembly related modules for improved startup performance

Commits

The new version differs by 8 commits.

dcc45dd 4.41.4
ab4fa8d Merge pull request #10146 from liximomo/fix-sideEffects
1452d19 test: add test case
156a087 fix: prevent incorrectly redirect
5b8fbca Merge pull request #10132 from jeffin143/patch-9859
e62512d Merge pull request #10133 from webpack/bugfix/issue-10104
77971bf backporting to webpack-4
c81963b fixes #10104

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.7.4 to 7.7.5.

The devDependency @babel/core was updated from 7.7.4 to 7.7.5.
The devDependency @babel/plugin-proposal-class-properties was updated from 7.7.0 to 7.7.4.
The devDependency @babel/plugin-proposal-object-rest-spread was updated from 7.6.2 to 7.7.4.
The devDependency @babel/plugin-transform-object-assign was updated from 7.2.0 to 7.7.4.
The devDependency @babel/plugin-transform-runtime was updated from 7.7.4 to 7.7.5.
The devDependency @babel/preset-env was updated from 7.7.4 to 7.7.5.
The devDependency @babel/preset-react was updated from 7.7.0 to 7.7.4.
The devDependency @babel/runtime was updated from 7.7.4 to 7.7.5.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for v7.7.5

v7.7.5 (2019-12-06)

🐛 Bug Fix

babel-plugin-transform-modules-commonjs, babel-plugin-transform-regenerator, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2
- #10549 Add ".js" extension to injected polyfill imports (@shimataro)
babel-cli
- #10283 babel --watch should have equivalent file selection logic with babel (@JLHwung)
babel-parser
- #10801 Use scope flags to check arguments (@JLHwung)
- #10800 Allow tuple rest trailing comma (@yeonjuan)
- #10475 Correctly disambiguate / after async fuctions (@nicolo-ribaudo)
babel-parser, babel-plugin-proposal-optional-chaining, babel-plugin-transform-modules-amd
- #10806 fix(optional chaining): Optional delete returns true with nullish base (@mpaarating)
babel-helper-module-transforms, babel-plugin-transform-modules-amd
- #10764 fix: rewriteBindingInitVisitor should skip on scopable node (@JLHwung)

💅 Polish

babel-plugin-transform-runtime
- #10788 Do not transpile typeof helper with itself in babel/runtime (@nicolo-ribaudo)
babel-core
- #10778 refactor: Improve error message in @babel/core (@jaroslav-kubicek)

🏠 Internal

babel-preset-env-standalone
- #10779 Bundle standalone using rollup (@JLHwung)
Other
- #10781 Tune makefile scripts (@JLHwung)
babel-helper-transform-fixture-test-runner
- #10566 Incorrect trace position in fixture runner (@JLHwung)

Committers: 8

Alex Lewis (@mpaarating)
Huáng Jùnliàng (@JLHwung)
Ives van Hoorne (@CompuIves)
Jaroslav Kubíček (@jaroslav-kubicek)
Kai Cataldo (@kaicataldo)
Nicolò Ribaudo (@nicolo-ribaudo)
YeonJuan (@yeonjuan)
shimataro (@shimataro)

Commits

The new version differs by 26 commits.

d04508e v7.7.5
d3a37b5 Add ".js" extension to injected polyfill imports (#10549)
c9a6898 babel --watch should have equivalent file selection logic with babel (#10283)
c6e966c [parser] Use scope flags to check arguments (#10801)
a0bed42 Bundle standalone using rollup (#10779)
2b47291 Tune makefile scripts (#10781)
e94da0d Incorrect trace position in fixture runner (#10566)
bb6cc61 fix(optional chaining): Optional delete returns true with nullish base (#10806)
3d0c5d2 Do not transpile typeof helper with itself in babel/runtime (#10788)
d18afbd Allow tuple rest trailing comma (#10800)
e74efd2 Run parser tests from the official TypeScript parser (#10444)
7195f0d Unify logic for running parser tests from external suites (#10444)
5440ae1 Correctly disambiguate / after async fuctions (#10475)
8f89167 Update core-js-compat (#10795)
26c0a32 refactor: Improve error message in @babel/core when root config is not found (#10778)

There are 26 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of lerna is breaking the build 🚨

The devDependency lerna was updated from `3.3.1` to `3.3.2`.

🚨 View failing branch.

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

lerna 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

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 9 commits.

96e1c00 chore(release): publish v3.3.2
3a7046c chore(ci): Split scripts one-per-line, maybe Windows likes that?
b0d23cd chore(ci): Run Windows CI on Azure
ba7667b chore(ci): i guess azure doesn't provide yarn automagically?
4e12d85 chore(ci): Use correct versionSpec key, quoted, setup git config
7c862a5 chore(ci): prettier has opionions, install latest npm
f8b0c8e chore: Set up CI with Azure Pipelines
b97d9a3 fix(publish): Allow --force-publish in a canary release
7971bf3 fix(version): Allow --force-publish to work on tagged releases

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of lerna is breaking the build 🚨

The devDependency lerna was updated from `3.15.0` to `3.16.0`.

🚨 View failing branch.

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

lerna 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

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v3.16.0

3.16.0 (2019-07-18)

Bug Fixes

command: Bump minimum range of lodash, silence dumb 'security' warning (c405871)
conventional-commits: Hard-pin lodash.template dependency to silence 'helpful' security warning (c54ad68)
deps: Bump @evocateur/pacote (03e4797)
deps: Update forked npm libs (4d67426)
npm-conf: OTP should default to undefined, figgy pudding is very strict (2fa02a8)
pack-directory: Bump npm-packlist + tar dependencies (59ebd19)
package-graph: Flatten cycles to avoid skipping packages (#2185) (b335763)
project: Ensure deprecated githubRelease config is also remapped from command.publish namespace (a3d264e), closes #2177
publish: Add --graph-type option to control packages included in topological sort (#2152) (ae87669), closes #1437
publish: Allow --no-verify-access to prevent checking for account-level 2FA (ce58d8f)
publish: OTP cache should be seeded from conf value, not CLI directly (cf56622)
publish: Propagate root license into custom publish directories (d410a58), closes #2157

Features

bootstrap: Add --strict option to enable throwing when --hoist warns (#2140) (91437b5)
deps: @octokit/plugin-enterprise-rest@^3.6.1 (74a3890)
deps: @octokit/rest@^16.28.4 (5f09f50)
deps: byte-size@^5.0.1 (ed51ddd)
deps: conventional-recommended-bump@^5.0.0 (2a0ed60)
deps: fs-extra@^8.1.0 (313287f)
deps: get-port@^4.2.0 (778ae6a)
deps: glob-parent@^5.0.0 (c6bc218)
deps: globby@^9.2.0 (d9aa249)
deps: import-local@^2.0.0 (14d2c66)
deps: is-ci@^2.0.0 (ab2ad83)
deps: load-json-file@^5.3.0 (3718cc9)
deps: multimatch@^3.0.0 (968b0d7)
deps: p-map@^2.1.0 (9e58394)
deps: pify@^4.0.1 (f8ee7e6)
deps: semver@^6.2.0 (d8016d9)
deps: slash@^2.0.0 (bedd6af)
deps: write-json-file@^3.2.0 (4fa7dea)
listable: Output JSON adjacency list with --graph (9457a21), closes #1970
otplease: Expose getOneTimePassword() helper (44b9f70)
publish: Eager prompt for OTP when account-level 2FA is enabled (4f893d1)
run-lifecycle: Upgrade npm-lifecycle@^3.1.0 (e015a74)

Commits

The new version differs by 53 commits.

8ca18be chore(release): v3.16.0
9457a21 feat(listable): Output JSON adjacency list with --graph
d410a58 fix(publish): Propagate root license into custom publish directories
6703a8e test(integration): Reduce flakiness of error message test
243b76d chore(deps): bump eslint-plugin-jest
91437b5 feat(bootstrap): Add --strict option to enable throwing when --hoist warns (#2140)
ae87669 fix(publish): Add --graph-type option to control packages included in topological sort (#2152)
b335763 fix(package-graph): Flatten cycles to avoid skipping packages (#2185)
e1b3d62 docs: Update instructions to use npm ci so tests pass, closes #2098 (#2172)
428a316 docs(add): Highlight single-argument limitation (#2174)
d935108 docs(version): remove unnecessary - (#2164)
6bd35e1 chore: reset lockfile
03e4797 fix(deps): Bump @evocateur/pacote
3ea00b9 chore(deps): Bump eslint-plugin-jest
5f09f50 feat(deps): @octokit/rest@^16.28.4

There are 53 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

1.0.0 An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.7.7 to 7.8.0.

The devDependency @babel/core was updated from 7.7.7 to 7.8.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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

❌ continuous-integration/drone/push: Build is failing (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of lerna is breaking the build 🚨

The devDependency lerna was updated from `3.14.1` to `3.14.2`.

🚨 View failing branch.

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

lerna 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

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v3.14.2

3.14.2 (2019-06-09)

Bug Fixes

bootstrap: Respect --force-local option (#2104) (c2fb639)
child-process: Ensure adjacent prefixes are always a different color (5a10146)
npm-publish: Use generated manifest when publishing subdirectory (b922766), closes #2113
publish: Allow per-leaf subdirectory publishing (ea861d9), closes #2109
version: Remove unused dependency (285bd7e)

Commits

The new version differs by 10 commits.

b22345b chore(release): v3.14.2
b922766 fix(npm-publish): Use generated manifest when publishing subdirectory
ea861d9 fix(publish): Allow per-leaf subdirectory publishing
c2fb639 fix(bootstrap): Respect --force-local option (#2104)
4f15361 docs(version): Fix typo in option header (#2120)
94fed60 docs: Add legacy fields to lerna.json section (#2108) [skip ci]
285bd7e fix(version): Remove unused dependency
5a10146 fix(child-process): Ensure adjacent prefixes are always a different color
c4d165a docs: Add disclaimer that Lerna is not a deployment tool (#2089)
9dc2bc5 docs: Indicate that even single-use deps are hoisted (#2090)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Logo

Something with wool and/or yarn.

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from `6.7.2` to `6.8.0`.

🚨 View failing branch.

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

eslint 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for v6.8.0

c5c7086 Fix: ignore aligning single line in key-spacing (fixes #11414) (#12652) (YeonJuan)
9986d9e Chore: add object option test cases in yield-star-spacing (#12679) (YeonJuan)
1713d07 New: Add no-error-on-unmatched-pattern flag (fixes #10587) (#12377) (ncraley)
5c25a26 Update: autofix bug in lines-between-class-members (fixes #12391) (#12632) (YeonJuan)
4b3cc5c Chore: enable prefer-regex-literals in eslint codebase (#12268) (薛定谔的猫)
05faebb Update: improve suggestion testing experience (#12602) (Brad Zacher)
05f7dd5 Update: Add suggestions for no-unsafe-negation (fixes #12591) (#12609) (Milos Djermanovic)
d3e43f1 Docs: Update no-multi-assign explanation (#12615) (Yuping Zuo)
272e4db Fix: no-multiple-empty-lines: Adjust reported loc (#12594) (Tobias Bieniek)
a258039 Fix: no-restricted-imports schema allows multiple paths/patterns objects (#12639) (Milos Djermanovic)
51f9620 Fix: improve report location for array-bracket-spacing (#12653) (Milos Djermanovic)
45364af Fix: prefer-numeric-literals doesn't check types of literal arguments (#12655) (Milos Djermanovic)
e3c570e Docs: Add example for expression option (#12694) (Arnaud Barré)
6b774ef Docs: Add spacing in comments for no-console rule (#12696) (Nikki Nikkhoui)
7171fca Chore: refactor regex in config comment parser (#12662) (Milos Djermanovic)
1600648 Update: Allow $schema in config (#12612) (Yordis Prieto)
acc0e47 Update: support .eslintrc.cjs (refs eslint/rfcs#43) (#12321) (Evan Plaice)
49c1658 Chore: remove bundling of ESLint during release (#12676) (Kai Cataldo)
257f3d6 Chore: complete to move to GitHub Actions (#12625) (Toru Nagashima)
ab912f0 Docs: 1tbs with allowSingleLine edge cases (refs #12284) (#12314) (Ari Kardasis)
dd1c30e Sponsors: Sync README with website (ESLint Jenkins)
a230f84 Update: include node version in cache (#12582) (Eric Wang)
8b65f17 Chore: remove references to parser demo (#12644) (Kai Cataldo)
e9cef99 Docs: wrap {{}} in raw liquid tags to prevent interpolation (#12643) (Kai Cataldo)
e707453 Docs: Fix configuration example in no-restricted-imports (fixes #11717) (#12638) (Milos Djermanovic)
19194ce Chore: Add tests to cover default object options in comma-dangle (#12627) (YeonJuan)
6e36d12 Update: do not recommend require-atomic-updates (refs #11899) (#12599) (Kai Cataldo)

Commits

The new version differs by 29 commits.

9738f8c 6.8.0
ba59cbf Build: changelog update for 6.8.0
c5c7086 Fix: ignore aligning single line in key-spacing (fixes #11414) (#12652)
9986d9e Chore: add object option test cases in yield-star-spacing (#12679)
1713d07 New: Add no-error-on-unmatched-pattern flag (fixes #10587) (#12377)
5c25a26 Update: autofix bug in lines-between-class-members (fixes #12391) (#12632)
4b3cc5c Chore: enable prefer-regex-literals in eslint codebase (#12268)
05faebb Update: improve suggestion testing experience (#12602)
05f7dd5 Update: Add suggestions for no-unsafe-negation (fixes #12591) (#12609)
d3e43f1 Docs: Update no-multi-assign explanation (#12615)
272e4db Fix: no-multiple-empty-lines: Adjust reported loc (#12594)
a258039 Fix: no-restricted-imports schema allows multiple paths/patterns objects (#12639)
51f9620 Fix: improve report location for array-bracket-spacing (#12653)
45364af Fix: prefer-numeric-literals doesn't check types of literal arguments (#12655)
e3c570e Docs: Add example for expression option (#12694)

There are 29 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of core-js is breaking the build 🚨

The devDependency core-js was updated from `3.4.5` to `3.4.6`.

🚨 View failing branch.

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

core-js 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for 3.4.6 - 2019.12.03

Improved iOS compat data - added missed mapping iOS 12.2 -> Safari 12.1, added bug fixes from patch releases
Added Safari 13.1 compat data
Added missed in core-js-compat helpers ie_mob normalization
Normalize the result of getModulesListForTargetVersion core-js-compat helper
Improved CI detection in the postinstall script, #707

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of core-js is breaking the build 🚨

The devDependency core-js was updated from `3.4.7` to `3.4.8`.

🚨 View failing branch.

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

core-js 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for 3.4.8 - 2019.12.09

Added one more workaround for broken in previous versions inspectSource helper, #719
Added Opera Mobile compat data
Updated Samsung Internet, iOS, old Node and Android compat data mapping
es.string.match-all marked as completely supported in FF73
Generate core-js-compat/modules since often we need just the list of core-js modules

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Discovery

https://developer.wordpress.org/rest-api/using-the-rest-api/discovery/

An in-range update of babel-plugin-transform-react-remove-prop-types is breaking the build 🚨

The devDependency babel-plugin-transform-react-remove-prop-types was updated from `0.4.20` to `0.4.21`.

🚨 View failing branch.

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

babel-plugin-transform-react-remove-prop-types 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

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v0.4.21

Add support for defining additionalLibraries as a regexp expression (#174) @pkuczynski

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Vue package

Create a new package called @yllet/vue to create vue bindings for yllet!

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.7.7 to 7.8.0.

The devDependency @babel/core was updated from 7.7.7 to 7.8.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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

❌ continuous-integration/drone/push: Build is failing (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

- The devDependency @babel/cli was updated from 7.7.5 to 7.7.7.

The devDependency @babel/core was updated from 7.7.5 to 7.7.7.
The devDependency @babel/plugin-proposal-object-rest-spread was updated from 7.7.4 to 7.7.7.
The devDependency @babel/preset-env was updated from 7.7.6 to 7.7.7.
The devDependency @babel/runtime was updated from 7.7.6 to 7.7.7.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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

❌ continuous-integration/drone/push: Build is failing (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Issue importing with Rollup

What I expected

Ability to bundle this package with rollup within another package.

What happened instead

Multiple errors with fs package (browser?) relating to form-data package.

Is this package isomorphic?

Steps to reproduce

import babel from "rollup-plugin-babel";
import json from "rollup-plugin-json";
import commonjs from "rollup-plugin-commonjs";
import includePaths from "rollup-plugin-includepaths";
import external from "rollup-plugin-peer-deps-external";
import builtins from "rollup-plugin-node-builtins";
import resolve from "rollup-plugin-node-resolve";

export default {
  input: "src/index.js",
  output: [
    {
      file: "dist/index.js",
      format: "cjs",
      sourcemap: true
    },
    {
      file: "dist/index.es.js",
      format: "es",
      sourcemap: true
    }
  ],
  plugins: [
    external(),
    builtins(),
    babel({
      exclude: /node_modules/,
      rootMode: "upward"
    }),
    json(),
    includePaths({
      paths: ["src"]
    }),
    resolve({ preferBuiltins: false }),
    commonjs()
  ]
};

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

github-actions

.github/workflows/node.yml

actions/checkout v3

actions/setup-node v3.7.0

npm

package.json

@types/jest ^28.1.8

@typescript-eslint/eslint-plugin ^6.0.0

@typescript-eslint/parser ^6.0.0

eslint ^8.44.0

isomorphic-fetch ^3.0.0

jest ^28.1.3

jest-mock 28.1.3

lerna ^4.0.0

prettier ^2.8.8

rimraf ^3.0.2

ts-jest ^28.0.8

typescript ^4.9.5

packages/client/package.json

isomorphic-form-data ^2.0.0

@types/isomorphic-form-data 2.0.1

fetch-mock ^9.11.0

packages/react/package.json

invariant ^2.2.4

prop-types ^15.8.1

@testing-library/jest-dom ^5.16.5

@testing-library/react ^13.4.0

@testing-library/react-hooks ^8.0.1

@types/invariant 2.2.35

jest-environment-jsdom ^28.1.3

@types/react ^18.2.17

react ^18.2.0

react-dom ^18.2.0

react *

packages/support/package.json

Check this box to trigger a request for Renovate to run again on this repository

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from `4.41.2` to `4.41.3`.

🚨 View failing branch.

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

webpack 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

❌ continuous-integration/drone/push: Build is failing (Details).

Release Notes for v4.41.3

Security

force upgrade terser-webpack-plugin dependency for security fix (not affecting webpack)

Funding

add npm funding field to package.json

Commits

The new version differs by 5 commits.

df9f3eb 4.41.3
fe71d68 Merge pull request #10010 from webpack/funding
b396d96 Merge pull request #10123 from pustovalov/webpack-4-serialize
29b2bdd Update terser-webpack-plugin to ^1.4.3
bedb566 chore: funding field

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

ylletjs / yllet Goto Github PK

yllet's People

Contributors

Stargazers

Watchers

Forkers

yllet's Issues

The devDependency core-js was updated from 3.5.0 to 3.6.0.

The devDependency core-js was updated from 3.4.4 to 3.4.5.

The devDependency core-js was updated from 3.4.3 to 3.4.4.

The devDependency rollup was updated from 1.27.5 to 1.27.6.

Bug Fixes

Pull Requests

The devDependency webpack was updated from 4.41.3 to 4.41.4.

Bugfixes

Performance

There have been updates to the babel7 monorepo:

v7.7.5 (2019-12-06)

🐛 Bug Fix

💅 Polish

🏠 Internal

Committers: 8

The devDependency lerna was updated from 3.3.1 to 3.3.2.

The devDependency lerna was updated from 3.15.0 to 3.16.0.

3.16.0 (2019-07-18)

Bug Fixes

Features

There have been updates to the babel7 monorepo:

The devDependency lerna was updated from 3.14.1 to 3.14.2.

3.14.2 (2019-06-09)

Bug Fixes

The devDependency eslint was updated from 6.7.2 to 6.8.0.

The devDependency core-js was updated from 3.4.5 to 3.4.6.

The devDependency core-js was updated from 3.4.7 to 3.4.8.

The devDependency babel-plugin-transform-react-remove-prop-types was updated from 0.4.20 to 0.4.21.

There have been updates to the babel7 monorepo:

Version 10 of Node.js (code name Dubnium) has been released! 🎊

There have been updates to the babel7 monorepo:

What I expected

What happened instead

Steps to reproduce

Open

Ignored or Blocked

Detected dependencies

The devDependency webpack was updated from 4.41.2 to 4.41.3.

Security

Funding

Recommend Projects

Recommend Topics

Recommend Org

The devDependency core-js was updated from `3.5.0` to `3.6.0`.

The devDependency core-js was updated from `3.4.4` to `3.4.5`.

The devDependency core-js was updated from `3.4.3` to `3.4.4`.

The devDependency rollup was updated from `1.27.5` to `1.27.6`.

The devDependency webpack was updated from `4.41.3` to `4.41.4`.

The devDependency lerna was updated from `3.3.1` to `3.3.2`.

The devDependency lerna was updated from `3.15.0` to `3.16.0`.

The devDependency lerna was updated from `3.14.1` to `3.14.2`.

The devDependency eslint was updated from `6.7.2` to `6.8.0`.

The devDependency core-js was updated from `3.4.5` to `3.4.6`.

The devDependency core-js was updated from `3.4.7` to `3.4.8`.

The devDependency babel-plugin-transform-react-remove-prop-types was updated from `0.4.20` to `0.4.21`.

The devDependency webpack was updated from `4.41.2` to `4.41.3`.