Git Product home page Git Product logo

inflate-auto's Introduction

InflateAuto

Build Status Coverage Dependency Status Supported Node Version Version on NPM

The InflateAuto class is designed to function as a drop-in replacement for zlib.Gunzip, zlib.Inflate, and zlib.InflateRaw when the method of compression is not known in advance. InflateAuto uses the first few bytes of data to determine the compression method (by checking for a valid gzip or zlib deflate header) then delegating the decompression work to the corresponding type.

Introductory Example

const InflateAuto = require('inflate-auto');
const assert = require('assert');
const zlib = require('zlib');

const testData = new Buffer('example data');
const compressor = Math.random() < 0.33 ? zlib.deflate :
      Math.random() < 0.5 ? zlib.deflateRaw :
      zlib.gzip;
compressor(testData, (errCompress, compressed) => {
  assert.ifError(errCompress);

  InflateAuto.inflateAuto(compressed, function(errDecompress, decompressed) {
    assert.ifError(errDecompress);
    assert.deepStrictEqual(decompressed, testData);
    console.log('Data compressed with random format and auto-decompressed.');
  });
});

Compatibility

InflateAuto should behave identically to any of the zlib decompression types, with the exception of instanceof and .constructor checks. Using the class should be as simple as s/Inflate(Raw)?/InflateAuto/g in existing code. If any real-world code requires modification (other than mentioned above) to work with InflateAuto it is considered a bug in InflateAuto. Please report any such issues.

Installation

This package can be installed using npm by running:

npm install inflate-auto

Recipes

Deflate HTTP

The primary use case for which this module was created is decompressing HTTP responses which declare Content-Encoding: deflate. As noted in Section 4.2.2 of RFC 7230 "Some non-conformant implementations send the "deflate" compressed data without the zlib wrapper." This has been attributed to early Microsoft servers and to old Apache mod_deflate, and is an issue in several less common servers. Regardless of the most common cause, it is observed in real-world behavior and poses a compatibility risk for HTTP clients which support deflate encoding. Using InflateAuto is one way to address the issue.

Compressed HTTP/HTTPS responses can be supported with code similar to the following:

const InflateAuto = require('inflate-auto');
const https = require('https');
const url = require('url');
const zlib = require('zlib');

const options = url.parse('https://api.stackexchange.com/2.2/answers?order=desc&sort=activity&site=stackoverflow');
options.headers = {
  Accept: 'application/json',
  'Accept-Encoding': 'gzip, deflate'
};
https.get(options, function(res) {
  const encoding =
    (res.headers['content-encoding'] || 'identity').trim().toLowerCase();

  // InflateAuto could be used for gzip to accept deflate data declared as gzip
  const inflater = encoding === 'deflate' ? new InflateAuto() :
    encoding === 'gzip' ? new zlib.Gunzip() :
    null;

  res.on('error', err => console.error('Response error:', err));

  let bodyData;
  if (inflater) {
    inflater.on('error', err => console.error('Decompression error:', err));
    bodyData = res.pipe(inflater);
  } else {
    bodyData = res;
  }

  bodyData.pipe(process.stdout, {end: false});
})
  .on('error', err => console.error('Request error:', err));

Log Compression Format

To be notified when the compression format is determined, listen for the 'format' event as follows:

const InflateAuto = require('inflate-auto');
const inflater = new InflateAuto();
inflater.on(
  'format',
  decoder => console.log('Compression format: ' + decoder.constructor.name)
);
inflater.write(compressedData);

Inflate Possibly-Compressed Data

By specifying PassThrough as the default format, InflateAuto can be used to inflate compressed data and pass through other data unchanged as follows:

const InflateAuto = require('inflate-auto');
const stream = require('stream');
const inflater = new InflateAuto({defaultFormat: stream.PassThrough});
inflater.pipe(process.stdout);
inflater.end(compressedOrUncompressedData);

Note that the above code would treat "raw" DEFLATE data as uncompressed since InflateRaw is normally the default format and is overridden with PassThrough. Feel free to open an issue to request support for detecting "raw" DEFLATE if this is desired.

Synchronous Inflate

Data can be decompressed while blocking the main thread using InflateAuto.inflateAutoSync (analogously to zlib.inflateSync) as follows:

const InflateAuto = require('inflate-auto');
const assert = require('assert');
const zlib = require('zlib');

const compressor = Math.random() < 0.33 ? zlib.deflateSync :
      Math.random() < 0.5 ? zlib.deflateRawSync :
      zlib.gzipSync;
const testData = new Buffer('example data');
const compressed = compressor(testData);
const decompressed = InflateAuto.inflateAutoSync(compressed);
assert.deepStrictEqual(decompressed, testData);

More examples can be found in the test specifications.

API Docs

For the details of using this module as a library, see the API Documentation.

Contributing

Contributions are appreciated. Contributors agree to abide by the Contributor Covenant Code of Conduct. If this is your first time contributing to a Free and Open Source Software project, consider reading How to Contribute to Open Source in the Open Source Guides.

If the desired change is large, complex, backwards-incompatible, can have significantly differing implementations, or may not be in scope for this project, opening an issue before writing the code can avoid frustration and save a lot of time and effort.

License

This project is available under the terms of the MIT License. See the summary at TLDRLegal.

inflate-auto's People

Contributors

dependabot-preview[bot] avatar dependabot[bot] avatar greenkeeper[bot] avatar kevinoid avatar

Stargazers

 avatar

Watchers

 avatar  avatar

inflate-auto's Issues

An in-range update of eslint-plugin-import is breaking the build ๐Ÿšจ

Version 2.9.0 of eslint-plugin-import was just published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-import
Current Version 2.8.0
Type devDependency

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

eslint-plugin-import 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 failed Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Commits

The new version differs by 101 commits.

  • 180d71a bump plugin to v2.9.0
  • 0231c78 Merge pull request #1026 from isiahmeadows/patch-1
  • ae5a031 Missed a link
  • 5b0777d Add no-default-export + docs/tests (#936)
  • ff3d883 Merge pull request #1025 from patrick-steele-idem/update-dependencies
  • 654d284 Merge pull request #1024 from patrick-steele-idem/issue-1023
  • 9b20a78 Upgraded "find-root" and "lodash.get" for the webpack resolver
  • 8778d7c Fixes #1023 - Load exceptions in user resolvers are not reported
  • 91cfd6d Merge pull request #1022 from nevir/patch-1
  • 0e729c7 no-self-import is unreleased
  • 219a8d2 Merge pull request #1012 from silvenon/extensions-export
  • ab49972 Support export declarations in extensions rule
  • 3268a82 Merge pull request #1010 from silvenon/extensions
  • fdcd4d9 Add a .coffee test proving extension resolve order
  • bc50394 Merge pull request #1009 from silvenon/extensions

There are 101 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 eslint-plugin-import is breaking the build ๐Ÿšจ

Version 2.3.0 of eslint-plugin-import just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-import
Current Version 2.2.0
Type devDependency

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

As eslint-plugin-import is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 46 commits.

  • b79e083 Merge pull request #837 from benmosher/release-2.3.0
  • 74425a2 changelog update for 2.3.0
  • 1377f55 bump v2.3.0
  • 2efc41a fix null pointer exception (#717) (#797)
  • 0fb592e Add support to specify the package.json (#685)
  • 2cc9768 Add test for flow type export (#835)
  • bd0e5e3 Merge pull request #821 from smably/patch-1
  • 412e518 Clarify docs for glob arrays
  • 106740f chore(package): update typescript-eslint-parser to version 2.1.0 (#790)
  • 6288cf9 chore(package): update babel-register to version 6.24.1 (#796)
  • 2e9eea6 newline-after-import test syntax fails
  • c9f10e8 extensions test fixes, attempt 2
  • 861765f fix babel syntax errors in extensions tests
  • 82f796c chore(package): update cross-env to version 4.0.0 (#783)
  • 98e7048 Merge pull request #757 from gmathieu/fix-default-keyword

There are 46 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of jsdoc is breaking the build ๐Ÿšจ

Version 3.5.0 of jsdoc just got published.

Branch Build failing ๐Ÿšจ
Dependency jsdoc
Current Version 3.4.3
Type devDependency

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

As jsdoc is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details
  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes JSDoc 3.5.0

This version of JSDoc includes the following major changes:

  • JSDoc now uses the Babylon JavaScript parser, which means that
    JSDoc can parse any JavaScript or JSX file that is supported by the Babel
    compiler.
  • You can now use a JavaScript file to configure JSDoc. See the
    documentation for details and examples.
  • Fixed multiple issues with documenting ES2015 classes and modules.
  • JSDoc now requires Node.js 4.2.0 or later.

For a complete list of changes, see the changelog on GitHub.

Commits

The new version differs by 112 commits ahead by 112, behind by 45.

  • cdd00c0 3.5.0
  • 50d6119 update 3.5.0 changelog
  • e94a598 3.5.0 changelog
  • 5d0b690 reformat changelog
  • c50a4c0 add yields tag (#1388)
  • f31a011 resolve the path to the JS config file before requiring it (#1386)
  • d95cbdd support namespaces that are also functions (#955)
  • 9f8853a add hideconstructor tag (#952)
  • ca1c4f2 add package tag (#962)
  • 6275e69 autodetect default and repeatable parameters when a function is assigned to a variable (#1054)
  • 0e4f1a9 correctly document constructors and instance properties of ES2015 classes (#1182)
  • 67db938 add sourceType config option
  • f101798 fix crash when the author tag is empty (#1289)
  • 43a117d add recurseDepth config option (#1340)
  • 8f5c60b support bigint

There are 112 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of bluebird is breaking the build ๐Ÿšจ

Version 3.5.2 of bluebird was just published.

Branch Build failing ๐Ÿšจ
Dependency bluebird
Current Version 3.5.1
Type devDependency

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

bluebird 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/appveyor/branch: AppVeyor build failed (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes v3.5.2

Bugfixes:

  • Fix PromiseRejectionEvent to contain .reason and .promise properties. (#1509, #1464)
  • Fix promise chain retaining memory until the entire chain is resolved (#1544, #1529)

id: changelog
title: Changelog

Commits

The new version differs by 22 commits.

  • 50067ec Release v3.5.2
  • f290da0 Fix memory being retained until promise queue is completely empty (#1544)
  • ad6d763 Update benchmarks (#1539)
  • 49da1ac Fix a typo. (#1534)
  • b06106a Fix typo in readme introduced in #1530 (#1531)
  • c1dc5b9 Update README.md (#1530)
  • e35455f chore: clone last 5 commits (#1521)
  • 91ae9ce chore: add Node.js 10 (#1523)
  • 9159472 Added a simple usage example (#1369)
  • 39081ba Update promise.each.md (#1479)
  • 77781fe Fix header (#1513)
  • b8eedc1 Update LICENSE to 2018 (#1490)
  • 4163e82 Added ES6 way to import the bluebird promise (#1461)
  • 3790a92 DOC: add direct link to Promise.delay from API ref (#1465)
  • e8d8525 Update error documentation (#1469)

There are 22 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 rimraf is breaking the build ๐Ÿšจ

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

๐Ÿšจ View failing branch.

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

rimraf 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 failed (Details).
  • โŒ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 6 commits.

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 jsdoc is breaking the build ๐Ÿšจ

The devDependency jsdoc was updated from 3.5.5 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.

jsdoc 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 105 commits ahead by 105, behind by 58.

  • 2099e72 3.6.0
  • d45c5b8 Add 3.6.0 changelog.
  • b8012f4 Update dependencies, plus the URLs for the GitHub repos and docs.
  • 10c004f update docs with new template (#1604)
  • aa0b6c1 switch to new-ish ECMAScript syntax
  • 1546d40 update ESLint config
  • 27f9a33 migrate from babylon to @babel/parser
  • d310908 Update ajv to the latest version ๐Ÿš€ (#1599)
  • ccb70aa only run CI with Node.js versions that actually exist
  • 2d3b55b migrate from markdown-it-named-headers to markdown-it-anchor (#1481)
  • 7b304d8 update dependencies and supported Node.js versions
  • b214273 3.5.5 changelog
  • 932c357 Prefer copyFileSync from here over native (#1440)
  • 8e2f868 upgrade Babylon
  • 96f8875 fix test breakage

There are 105 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 safe-buffer is breaking the build ๐Ÿšจ

Version 5.1.2 of safe-buffer was just published.

Branch Build failing ๐Ÿšจ
Dependency safe-buffer
Current Version 5.1.1
Type devDependency

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

safe-buffer 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/appveyor/branch Waiting for AppVeyor build to complete Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 10 commits.

  • 649435c 5.1.2
  • d58337d travis: explicitly test node 10
  • 39eb1c4 remove unused zuul dependency
  • 0f01e1b npmignore
  • 561bf4a test: move to test/ folder
  • d3f0a33 Merge pull request #21 from machinomy/master
  • 9bcb112 Add TypeScript type declarations
  • dbd588c Merge pull request #16 from MarkHerhold/patch-1
  • 76fb90c Test against Node.js LTS versions
  • c600c4f remove package-lock.json

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-plugin-import is breaking the build ๐Ÿšจ

Version 2.5.0 of eslint-plugin-import just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-import
Current Version 2.3.0
Type devDependency

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

As eslint-plugin-import is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 27 commits.

  • c41ed06 bump to v2.5.0
  • 94187a3 bump debug version everywhere
  • 54687d1 resolvers/webpack: v0.8.2
  • dac23a1 eslint-module-utils: v2.1.1 (bumping to re-publish to npm)
  • d92ef43 Merge pull request #696 from eelyafi/new_line_fixer
  • 3f9e4bf [Tests] comment out failing (and probably invalid) test
  • 4067495 Only apps should have lockfiles.
  • ebaa8e3 Merge pull request #873 from lukeapage/patch-3
  • 3268cb1 Fix documentation of newline-after-import example
  • 3c46d30 rollback utils dependency to 2.0.0
  • e3a32ad add yank note to utils change log
  • 089f7f1 add yanking note to root change log
  • dfbe0e7 Upgrade debug version of eslint-module-utils (#844)
  • 3d9c642 Merge branch 'release'
  • b8e9a0b Merge pull request #861 from benmosher/release-2.4.0

There are 27 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint-config-airbnb-base is breaking the build ๐Ÿšจ

Version 11.3.0 of eslint-config-airbnb-base just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-config-airbnb-base
Current Version 11.2.0
Type devDependency

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

As eslint-config-airbnb-base is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint-plugin-import is breaking the build ๐Ÿšจ

Version 2.4.0 of eslint-plugin-import just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-import
Current Version 2.3.0
Type devDependency

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

As eslint-plugin-import is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 10 commits.

  • 44ca158 update utils changelog
  • a3728d7 bump eslint-module-utils to v2.1.0
  • 3e29169 bump v2.4.0
  • ea9c92c Merge pull request #737 from kevin940726/master
  • 8f9b403 fix typos, enforce type of array of strings in allow option
  • 95315e0 update CHANGELOG.md
  • 28e1623 eslint-module-utils: filePath in parserOptions (#840)
  • 2f690b4 update CI to build on Node 6+7 (#846)
  • 7d41745 write doc, add two more tests
  • dedfb11 add allow glob for rule no-unassigned-import, fix #671

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint is breaking the build ๐Ÿšจ

Version 4.7.1 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 4.7.0
Type devDependency

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

As eslint is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details
  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v4.7.1
  • 08656db Fix: Handle nested disable directive correctly (fixes #9318) (#9322) (Gyandeep Singh)
  • 9226495 Revert "Chore: rewrite parseListConfig for a small perf gain." (#9325) (่–›ๅฎš่ฐ”็š„็Œซ)
Commits

The new version differs by 4 commits.

  • 2f064d9 4.7.1
  • 0d0bd7b Build: changelog update for 4.7.1
  • 08656db Fix: Handle nested disable directive correctly (fixes #9318) (#9322)
  • 9226495 Revert "Chore: rewrite parseListConfig for a small perf gain." (#9325)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint is breaking the build ๐Ÿšจ

Version 4.12.0 of eslint was just published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 4.11.0
Type devDependency

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 failed Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Release Notes v4.12.0
  • 76dab18 Upgrade: doctrine@^2.0.2 (#9656) (Kevin Partington)
  • 28c9c8e New: add a Linter#defineParser function (#9321) (Ives van Hoorne)
  • 5619910 Update: Add autofix for sort-vars (#9496) (Trevin Hofmann)
  • 71eedbf Update: add beforeStatementContinuationChars to semi (fixes #9521) (#9594) (Toru Nagashima)
  • 4118f14 New: Adds implicit-arrow-linebreak rule (refs #9510) (#9629) (Sharmila Jesupaul)
  • 208fb0f Fix: Use XML 1.1 on XML formatters (fixes #9607) (#9608) (Daniel Reigada)
  • 6e04f14 Upgrade: globals to 11.0.1 (fixes #9614) (#9632) (Toru Nagashima)
  • e13d439 Fix: space-in-parens crash (#9655) (Toru Nagashima)
  • 92171cc Docs: Updating migration guide for single-line disable (#9385) (Justin Helmer)
  • f39ffe7 Docs: remove extra punctuation from readme (#9640) (Teddy Katz)
  • a015234 Fix: prefer-destructuring false positive on "super" (fixes #9625) (#9626) (Kei Ito)
  • 0cf081e Update: add importNames option to no-restricted-imports (#9506) (Benjamin R Gibson)
  • 332c214 Docs: Add @platinumazure to TSC (#9618) (Ilya Volodin)
Commits

The new version differs by 15 commits.

  • f4a65c6 4.12.0
  • 1cd1627 Build: changelog update for 4.12.0
  • 76dab18 Upgrade: doctrine@^2.0.2 (#9656)
  • 28c9c8e New: add a Linter#defineParser function (#9321)
  • 5619910 Update: Add autofix for sort-vars (#9496)
  • 71eedbf Update: add beforeStatementContinuationChars to semi (fixes #9521) (#9594)
  • 4118f14 New: Adds implicit-arrow-linebreak rule (refs #9510) (#9629)
  • 208fb0f Fix: Use XML 1.1 on XML formatters (fixes #9607) (#9608)
  • 6e04f14 Upgrade: globals to 11.0.1 (fixes #9614) (#9632)
  • e13d439 Fix: space-in-parens crash (#9655)
  • 92171cc Docs: Updating migration guide for single-line disable (#9385)
  • f39ffe7 Docs: remove extra punctuation from readme (#9640)
  • a015234 Fix: prefer-destructuring false positive on "super" (fixes #9625) (#9626)
  • 0cf081e Update: add importNames option to no-restricted-imports (#9506)
  • 332c214 Docs: Add @platinumazure to TSC (#9618)

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-plugin-import is breaking the build ๐Ÿšจ

โ˜๏ธ Greenkeeperโ€™s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.11.0 of eslint-plugin-import was just published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-import
Current Version 2.10.0
Type devDependency

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

eslint-plugin-import 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 failed Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Commits

The new version differs by 21 commits.

  • e0dcfbd Merge branch 'fix-perf' into release-2.10.1 (fixes #1058)
  • 774ea8d changelog note for #1058
  • 7bd2775 perf: no AST nodes in caches
  • 83c85fc bump to v2.11.0 for #880 (semver-minor)
  • 54e3013 changelog for #880
  • 0ff8f23 bump to v2.10.1
  • f0b4f3e Merge pull request #1069 from ljharb/resolve
  • fb8e1e5 [patch] use resolve instead of builtin-modules
  • d8077c8 Merge pull request #1064 from ljharb/fix_no_cycle
  • 80d1ceb Merge pull request #1065 from sharmilajesupaul/minor-typo-fix
  • f13f18e minor typo in import/no-cycle rule docs
  • 19fc3df [Fix] no-cycle: create must always return an object, even if thereโ€™s no listeners
  • ee15fa4 Merge pull request #880 from futpib/no-commonjs-allow-require
  • 48d0a8a changelog note for #1046
  • a2acbde add fixer for first (#1046)

There are 21 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 eslint is breaking the build ๐Ÿšจ

Version 4.11.0 of eslint was just published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 4.10.0
Type devDependency

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 failed Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Release Notes v4.11.0
  • d4557a6 Docs: disallow use of the comma operator using no-restricted-syntax (#9585) (่–›ๅฎš่ฐ”็š„็Œซ)
  • d602f9e Upgrade: espree v3.5.2 (#9611) (Kai Cataldo)
  • 4def876 Chore: avoid handling rules instances in config-validator (#9364) (Teddy Katz)
  • fe5ac7e Chore: fix incorrect comment in safe-emitter.js (#9605) (Teddy Katz)
  • 6672fae Docs: Fixed a typo on lines-between-class-members doc (#9603) (Moinul Hossain)
  • 980ecd3 Chore: Update copyright and license info (#9599) (่–›ๅฎš่ฐ”็š„็Œซ)
  • cc2c7c9 Build: use Node 8 in appveyor (#9595) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 2542f04 Docs: Add missing options for lines-around-comment (#9589) (Clรฉment Fiorio)
  • b6a7490 Build: ensure fuzzer tests get run with npm test (#9590) (Teddy Katz)
  • 1073bc5 Build: remove shelljs-nodecli (refs #9533) (#9588) (Teddy Katz)
  • 7e3bf6a Fix: edge-cases of semi-style (#9560) (Toru Nagashima)
  • e5a37ce Fix: object-curly-newline for flow code (#9458) (Tiddo Langerak)
  • 9064b9c Chore: add equalTokens in ast-utils. (#9500) (่–›ๅฎš่ฐ”็š„็Œซ)
  • b7c5b19 Fix: Correct [object Object] output of error.data. (#9561) (Jonathan Pool)
  • 51c8cf0 Docs: Disambiguate definition of Update tag (#9584) (Jonathan Pool)
  • afc3c75 Docs: clarify what eslint-config-eslint is (#9582) (Teddy Katz)
  • aedae9d Docs: fix spelling in valid-typeof example (#9574) (Maksim Degtyarev)
  • 4c5aaf3 Docs: Fix typo in no-underscore-dangle rule (#9567) (Fabien Lucas)
  • 3623600 Chore: upgrade [email protected] (#9557) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 1b606cd Chore: Remove an indirect dependency on jsonify (#9444) (Rouven WeรŸling)
  • 4d7d7ab Update: Resolve npm installed formatters (#5900) (#9464) (Tom Erik Stรธwer)
  • accc490 Fix: Files with no failures get "passing" testcase (#9547) (Samuel Levy)
  • ab0f66d Docs: Add examples to better show rule coverage. (#9548) (Jonathan Pool)
  • 88d2303 Chore: Add object-property-newline tests to increase coverage. (#9553) (Jonathan Pool)
  • 7f37b1c Build: test Node 9 on Travis (#9556) (Teddy Katz)
  • acccfbd Docs: Minor rephrase in no-invalid-this. (#9542) (Francisc)
  • 8f9c0fe Docs: improve id-match usage advice (#9544) (Teddy Katz)
  • a9606a3 Fix: invalid tests with super (fixes #9539) (#9545) (Teddy Katz)
  • 8e1a095 Chore: enable a modified version of multiline-comment-style on codebase (#9452) (Teddy Katz)
  • cb60285 Chore: remove commented test for HTML formatter (#9532) (Teddy Katz)
  • 06b491e Docs: fix duplicate entries in changelog (#9530) (Teddy Katz)
  • 2224733 Chore: use eslint-plugin-rulesdir instead of --rulesdir for self-linting (#9164) (Teddy Katz)
  • 9cf4ebe Docs: add .md to link(for github users) (#9529) (่–›ๅฎš่ฐ”็š„็Œซ)
Commits

The new version differs by 35 commits.

  • 1a9a6a5 4.11.0
  • ef4d268 Build: changelog update for 4.11.0
  • d4557a6 Docs: disallow use of the comma operator using no-restricted-syntax (#9585)
  • d602f9e Upgrade: espree v3.5.2 (#9611)
  • 4def876 Chore: avoid handling rules instances in config-validator (#9364)
  • fe5ac7e Chore: fix incorrect comment in safe-emitter.js (#9605)
  • 6672fae Docs: Fixed a typo on lines-between-class-members doc (#9603)
  • 980ecd3 Chore: Update copyright and license info (#9599)
  • cc2c7c9 Build: use Node 8 in appveyor (#9595)
  • 2542f04 Docs: Add missing options for lines-around-comment (#9589)
  • b6a7490 Build: ensure fuzzer tests get run with npm test (#9590)
  • 1073bc5 Build: remove shelljs-nodecli (refs #9533) (#9588)
  • 7e3bf6a Fix: edge-cases of semi-style (#9560)
  • e5a37ce Fix: object-curly-newline for flow code (#9458)
  • 9064b9c Chore: add equalTokens in ast-utils. (#9500)

There are 35 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 ๐ŸŒด

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.