simenb / util.promisify-all

util.promisify-all

'util.promisify' for objects. Uses util.promisify under the hood.

Example:

const promisify = require('util.promisify-all');

const fs = promisify(require('fs'));

fs.readFile('/tmp/file.txt')
  .then(console.log)
  .catch(console.error);

util.promisify-all's Issues

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

The devDependency eslint-config-simenb-base was updated from 15.0.0 to 15.0.1.

🚨 View failing branch.

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

eslint-config-simenb-base 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).

---

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 🌴

module.exports is a function?

function foo(callback) {}
foo.bar = function bar(callback) {};
module.exports = foo;

How does promisify-all work with this module?

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

The devDependency eslint was updated from 5.12.0 to 5.12.1.

🚨 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/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v5.12.1

• eb5c401 Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773) (薛定谔的猫)
• aa56247 Fix: avoid loading core rules dynamically from FS in Linter (#11278) (Peter Metz)
• 04450bb Docs: clarify process for adding committers (#11272) (Kai Cataldo)
• 3ffcf26 Docs: add @g-plane as committer (#11277) (Kai Cataldo)
• c403445 Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253) (Merlin Mason)
• 9194f45 Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221) (Gabriel Cousin)
• 000f495 Docs: fix example for sort-imports ignoreDeclarationSort (#11242) (Remco Haszing)
• 7c0bf2c Docs: Add npx usage to Getting Started guide (#11249) (eyal0803)
• da9174e Docs: fixes typo peerDepencies (#11252) (Christian Kühl)
• 9c31625 Docs: Improve custom formatter docs (#11258) (Nicholas C. Zakas)

Commits

The new version differs by 12 commits.

• faf3c4e 5.12.1
• 1010c98 Build: changelog update for 5.12.1
• eb5c401 Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773)
• aa56247 Fix: avoid loading core rules dynamically from FS in Linter (#11278)
• 04450bb Docs: clarify process for adding committers (#11272)
• 3ffcf26 Docs: add @g-plane as committer (#11277)
• c403445 Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253)
• 9194f45 Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221)
• 000f495 Docs: fix example for sort-imports ignoreDeclarationSort (#11242)
• 7c0bf2c Docs: Add npx usage to Getting Started guide (#11249)
• da9174e Docs: fixes typo peerDepencies (#11252)
• 9c31625 Docs: Improve custom formatter docs (#11258)

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 eslint is breaking the build 🚨

The devDependency eslint was updated from 5.15.3 to 5.16.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/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v5.16.0

• dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567) (Kevin Partington)
• c06d38c Fix: Allow HTML formatter to handle no meta data (#11566) (Ilya Volodin)
• 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548) (Oliver Joseph Ash)
• bc3e427 Update: pass rule meta to formatters RFC 10 (#11551) (Chris Meyer)
• b452f27 Chore: Update README to pull in reviewer data (#11506) (Nicholas C. Zakas)
• afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550) (Vernon de Goede)
• 4fe7eb7 Chore: use nyc instead of istanbul (#11532) (Toru Nagashima)
• f16af43 Chore: fix formatters/table test (#11534) (Toru Nagashima)
• 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528) (Teddy Katz)

Commits

The new version differs by 11 commits.

• ded2f94 5.16.0
• ea36e13 Build: changelog update for 5.16.0
• dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567)
• c06d38c Fix: Allow HTML formatter to handle no meta data (#11566)
• 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548)
• bc3e427 Update: pass rule meta to formatters RFC 10 (#11551)
• b452f27 Chore: Update README to pull in reviewer data (#11506)
• afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550)
• 4fe7eb7 Chore: use nyc instead of istanbul (#11532)
• f16af43 Chore: fix formatters/table test (#11534)
• 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528)

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 prettier is breaking the build 🚨

The devDependency prettier was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

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

prettier 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 1.14.3

🔗 Changelog

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 object.entries is breaking the build 🚨

The dependency object.entries was updated from 1.0.4 to 1.1.0.

🚨 View failing branch.

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

object.entries is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

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 12 commits.

• e19be64 v1.1.0
• 89415ba [Tests] up to node v11.6, v10.15, v8.15, v6.16
• 074677d [Dev Deps] update eslint, @ljharb/eslint-config, covert, tape
• bc3e6a7 [Tests] use npm audit instead of nsp
• 052aed1 [Tests] remove jscs
• 0015678 [Tests] up to node v11.1, v10.13, v9.11, v8.12, v7.10, v6.14, v4.9; use nvm install-latest-npm
• 91f9ee6 [Dev Deps] update eslint, @ljharb/eslint-config, nsp, tape
• 9799c0d [New] add auto entry point`
• db5d97e [Deps] update define-properties, es-abstract, function-bind, has
• d192ab7 Only apps should have lockfiles
• 6f19e66 [Tests] up to node v7.4, v4.7; improve test matrix
• 3ae9c91 Exclude test.html from the npm package.

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 🌴