Coder Social home page Coder Social logo

espresso's People

Contributors

azure-pipelines[bot] avatar dependabot[bot] avatar github-actions[bot] avatar greenkeeper[bot] avatar renovate[bot] avatar stefanschoof avatar

Stargazers

avatar

Watchers

avatar avatar avatar avatar

Forkers

yaananth tomsungit

espresso's Issues

An in-range update of @types/applicationinsights-js is breaking the build 🚨

The devDependency @types/applicationinsights-js was updated from 1.0.7 to 1.0.8.

🚨 View failing branch.

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

@types/applicationinsights-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
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.2 to 5.15.3.

🚨 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
Release Notes for v5.15.3
  • 71adc66 Fix: avoid moving comments in implicit-arrow-linebreak (fixes #11521) (#11522) (Teddy Katz)
  • 1f715a2 Chore: make test-case-property-ordering reasonable (#11511) (Toru Nagashima)
Commits

The new version differs by 4 commits.

  • a6168f8 5.15.3
  • cb57316 Build: changelog update for 5.15.3
  • 71adc66 Fix: avoid moving comments in implicit-arrow-linebreak (fixes #11521) (#11522)
  • 1f715a2 Chore: make test-case-property-ordering reasonable (#11511)

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 @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from 24.0.10 to 24.0.11.

🚨 View failing branch.

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

@types/jest 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
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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.12.11 to 10.12.12.

🚨 View failing branch.

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

@types/node 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
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 azure-iot-device-mqtt is breaking the build 🚨

The dependency azure-iot-device-mqtt was updated from 1.7.5 to 1.8.0.

🚨 View failing branch.

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

azure-iot-device-mqtt 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
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-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.2.1 to 3.3.0.

🚨 View failing branch.

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

webpack-dev-server 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
Release Notes for v3.3.0

3.3.0 (2019-04-08)

Bug Fixes

Features

  • add option "serveIndex" to enable/disable serveIndex middleware (#1752) (d5d60cb)
  • add webpack as argument to before and after options (#1760) (0984d4b)
  • http2 option to enable/disable HTTP/2 with HTTPS (#1721) (dcd2434)
  • random port retry logic (#1692) (419f02e)
  • relax depth limit from chokidar for content base (#1697) (7ea9ab9)
Commits

The new version differs by 34 commits.

  • 99e8db0 chore(release): 3.3.0
  • df3ee67 test: refactor (#1768)
  • f61dfd4 test: compress option (#1766)
  • 919ff77 fix(Server): validate express.static.mime.types (#1765)
  • 1b3cd4f chore(deps): update dependency marked to v0.6.2 (#1764)
  • d5d60cb feat: add option "serveIndex" to enable/disable serveIndex middleware (#1752)
  • abf8691 Pass mimeTypes option to webpack-dev-middleware (#1714)
  • 05b8fb7 style: add curly rule to eslint (#1761)
  • dcd2434 feat: http2 option to enable/disable HTTP/2 with HTTPS (#1721)
  • 0984d4b feat: add webpack as argument to before and after options (#1760)
  • 31dfe22 chore(deps): update (#1759)
  • 737171e chore(deps): update dependency supertest to v4 (#1757)
  • 0429113 chore(deps): update all minor dependencies (#1756)
  • 5b55110 chore(deps): update all patch dependencies (patch) (#1755)
  • e65705b chore(deps): pin dependencies (#1705)

There are 34 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 webpack-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.5.0 to 3.5.1.

🚨 View failing branch.

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

webpack-dev-server 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
Release Notes for v3.5.1

3.5.1 (2019-06-01)

Bug Fixes

  • allow passing promise function of webpack.config.js (#1947) (8cf1053)
Commits

The new version differs by 5 commits.

  • def98d8 chore(release): 3.5.1
  • ffb2c79 refactor(client): separate into modules (#1948)
  • fb31770 refactor: utils and server (#1943)
  • 8cf1053 fix: allow passing promise function of webpack.config.js (#1947)
  • 03c2751 chore(deps): update dependency memfs to ^2.15.4 (#1949)

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
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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.12.19 to 10.12.20.

🚨 View failing branch.

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

@types/node 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
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 applicationinsights is breaking the build 🚨

The dependency applicationinsights was updated from 1.2.0 to 1.3.0.

🚨 View failing branch.

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

applicationinsights 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
Commits

The new version differs by 1 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 webpack-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.3.4 to 3.3.5.

🚨 View failing branch.

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

webpack-cli 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
Release Notes for Webpack CLI v3.3.5

Webpack-CLI v3.3.5 has a patch to remove the donation banner that causes some irritation around donations to webpack and for windows users. We've removed this and a full changelog is found here

Commits

The new version differs by 16 commits.

  • 30b1b8d chore: v3.3.5
  • 76b75ac chore: remove donation section
  • 8913928 chore: update pkg lock
  • a37477d cli: remove donation prompt
  • 002a6ac Merge pull request #970 from dhruvdutt/postinstall
  • cd54ba5 chore(scripts): clean opencollective
  • 0c1f6b6 chore(scripts): clean postinstall
  • 313e83e chore(deps): update major versions (#969)
  • 6105ef1 fix(deps): move prettier from dependencies to devDependencies (#968)
  • dad54f4 chore(ts): enables source map in the ts (#961)
  • d7cdab9 Merge pull request #960 from DanielRuf/fix/use-strict
  • 6015bad chore: added await in order to resolve the pending promise (#948)
  • 670efc7 fix: change "usr strict" to "use strict"
  • dc25beb Merge pull request #959 from webpack/fix/deps
  • 69f364e fix: update deps

There are 16 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 @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 1.11.0 to 1.12.0.

🚨 View failing branch.

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

@typescript-eslint/parser 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
Release Notes for v1.12.0

1.12.0 (2019-07-12)

Bug Fixes

  • eslint-plugin: handle const; (#633) (430d628), closes #441
  • typescript-estree: fix async identifier token typed as Keyword (#681) (6de19d3)

Features

  • eslint-plugin: [ban-types] Support namespaced type (#616) (e325b72)
  • eslint-plugin: [explicit-function-return-type] add handling for usage as arguments (#680) (e0aeb18)
  • eslint-plugin: [no-explicit-any] Add an optional fixer (#609) (606fc70)
  • eslint-plugin: Add rule no-reference-import (#625) (af70a59)
  • eslint-plugin: add rule strict-boolean-expressions (#579) (34e7d1e)
  • eslint-plugin: added new rule prefer-readonly (#555) (76b89a5)
Commits

The new version differs by 13 commits.

  • cd96c38 chore: publish v1.12.0
  • b30e78d chore(deps): bump lodash.template from 4.4.0 to 4.5.0 (#693)
  • e0aeb18 feat(eslint-plugin): [explicit-function-return-type] add handling for usage as arguments (#680)
  • 6de19d3 fix(typescript-estree): fix async identifier token typed as Keyword (#681)
  • af70a59 feat(eslint-plugin): Add rule no-reference-import (#625)
  • 34e7d1e feat(eslint-plugin): add rule strict-boolean-expressions (#579)
  • 44677b4 docs(eslint-plugin): format array-type docs
  • 44b099d docs(eslint-plugin): Expand docs for array-type (#634)
  • b83ff5a docs: add link to eslint support in TS repo (#650)
  • 430d628 fix(eslint-plugin): handle const; (#633)
  • e325b72 feat(eslint-plugin): [ban-types] Support namespaced type (#616)
  • 606fc70 feat(eslint-plugin): [no-explicit-any] Add an optional fixer (#609)
  • 76b89a5 feat(eslint-plugin): added new rule prefer-readonly (#555)

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 @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from 24.0.6 to 24.0.7.

🚨 View failing branch.

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

@types/jest 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
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-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.3.5 to 3.3.6.

🚨 View failing branch.

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

webpack-cli 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
Release Notes for Webpack CLI v3.3.6

Webpack CLI v3.3.6 is a security patch that fixes vulnerabilities. Please upgrade if not done so already. A full changelog available here

Stay safe🙏🏽

Commits

The new version differs by 12 commits.

  • a56e916 chore: v3.3.6
  • 110fa5e chore: fix sec vuln
  • 6c766f8 Merge pull request #974 from jamesgeorge007/feat/minor-refactor
  • 7978d77 Merge pull request #975 from pranshuchittora/chore-typo
  • ba471f8 chore: prevent weird behaviour of pre-commit hook (#973)
  • 49e4adc docs: remove deprecated packages description (#979)
  • a30a027 fix: minor refactor
  • 7553ae7 fix: update comments
  • 941da90 chore: include comments
  • 0d9aa9a fix: minor fix
  • d2e3e80 chore(serve): refactor code to be more concise
  • bd5c1ce chore(utils): fixes typo in scaffold

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 azure-iot-device is breaking the build 🚨

The dependency azure-iot-device was updated from 1.7.5 to 1.8.0.

🚨 View failing branch.

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

azure-iot-device 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
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 azure-iot-device is breaking the build 🚨

The dependency azure-iot-device was updated from 1.9.9 to 1.10.0.

🚨 View failing branch.

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

azure-iot-device 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
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-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.5.1 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.

webpack-dev-server 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
Release Notes for v3.6.0

3.6.0 (2019-06-05)

Bug Fixes

Features

Commits

The new version differs by 17 commits.

  • 9582418 chore(release): 3.6.0
  • 699f8b4 fix(server): don't ignore node_modules by default (#1970)
  • 53f4253 chore(deps): update dependency webpack to ^4.33.0 (#1966)
  • dc81e23 fix(config): enable --overlay (#1968)
  • 0783a4a test: change jest.setTimeout from 20000 to 30000 (#1965)
  • 397bec8 docs(options): added urls for new inject options (#1959)
  • 428f410 chore(deps): update dependency commitlint-azure-pipelines-cli to ^1.0.2 (#1964)
  • 2a03295 chore(deps): delete nyc dependency (#1962)
  • 27eb99c test: delete temp directory (#1958)
  • 79325e5 test(client): add tests for default/index.js (#1957)
  • d346a53 test(server): add SockJSServer test (#1956)
  • eecc1e4 refactor: insert client implementation from within Dev Server API (#1933)
  • 6973e4c refactor(client): create log module into utils (#1953)
  • 1581adc refactor(client): create createSocketUrl module into utils (#1954)
  • 9a1ad89 test(routes): stop checking for res.text (#1952)

There are 17 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 @typescript-eslint/eslint-plugin is breaking the build 🚨

The devDependency @typescript-eslint/eslint-plugin was updated from 1.9.0 to 1.10.0.

🚨 View failing branch.

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

@typescript-eslint/eslint-plugin 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
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 @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 1.4.1 to 1.4.2.

🚨 View failing branch.

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

@typescript-eslint/parser 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
Release Notes for v1.4.2

This is a republishing of v1.4.1, which had incomplete dist artifacts, sorry for any inconvenience!

Commits

The new version differs by 2 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 webpack is breaking the build 🚨

The devDependency webpack was updated from 4.35.2 to 4.35.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
Release Notes for v4.35.3

Bugfixes

  • update acorn to include import()

Performance

  • Improved runtime performance for large JSON modules
Commits

The new version differs by 20 commits.

  • 4ec90ce 4.35.3
  • 91a211e Merge pull request #9378 from webpack/dependabot/npm_and_yarn/ajv-6.10.1
  • 0db2c54 Merge pull request #9377 from webpack/dependabot/npm_and_yarn/ajv-keywords-3.4.1
  • 30ddec0 chore(deps): bump ajv from 6.10.0 to 6.10.1
  • 1b54416 chore(deps): bump ajv-keywords from 3.4.0 to 3.4.1
  • f092150 Merge pull request #9370 from DRoet/dynamic-import
  • b56c3ec feat: update acorn for dynamic import
  • 0976bd3 Merge pull request #9363 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.7.2
  • 45acc86 Merge pull request #9361 from webpack/dependabot/npm_and_yarn/acorn-6.2.0
  • dfeb9a9 Merge pull request #9359 from webpack/dependabot/npm_and_yarn/types/node-10.14.12
  • db85be0 chore(deps-dev): bump eslint-plugin-jest from 22.7.1 to 22.7.2
  • 219f773 chore(deps): bump acorn from 6.1.1 to 6.2.0
  • 72e0540 chore(deps-dev): bump @types/node from 10.14.10 to 10.14.12
  • 0af4549 Merge pull request #9356 from webpack/dependabot/npm_and_yarn/simple-git-1.118.0
  • 1ce0c21 chore(deps-dev): bump simple-git from 1.117.0 to 1.118.0

There are 20 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 @microsoft/applicationinsights-web is breaking the build 🚨

The dependency @microsoft/applicationinsights-web was updated from 2.0.1 to 2.1.0.

🚨 View failing branch.

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

@microsoft/applicationinsights-web 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
Release Notes for 2.1.0

2.1.0 Highlights

Source Map Support

*You do not need to upgrade for drag and drop to work. It will work on all previous and future versions of the javascript (and Node.js) SDK
https://i.imgur.com/Efue9nU.gif
You can now drag and drop your source maps onto your Exception Telemetry in the Azure Portal to unminify your callstack. Please open an issue or use the Feedback button in the Portal if a source map you've uploaded is not working as intended. This is a first iteration and in a future update, your source maps will be automatically unminified.

SPA Route Change Tracking

You can set enableAutoRouteTracking: true to enable state based route tracking for your Single Page Application (React, Angular, Vue, etc). You do not need to install a separate plugin to use this configuration option.

This setting will cause a new Page View telemetry item to be sent each time your app's route changes (including Hash route changes).

Request/Response Header Tracking

Changelog

  • #920 Resolve jest testing issues when using React plugin
  • #928 Make analytics plugin have last priority
  • #936 Fallback to XHR Sender when beacon sender tries to send >64 KB
  • #947 Add SPA route change tracking
  • #946 Add new feature to track request & response headers
  • #948 Docs: Source map support
  • #952 Re-enable samplingPercentage functionality
  • #918, #919, #932 #933 #935 #939 #940 #951
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.28.0 to 4.28.1.

🚨 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
Release Notes for v4.28.1

Bugfixes

  • fix error in IgnorePlugin when no contextRegExp is passed
Commits

The new version differs by 3 commits.

  • 7a6a71f 4.28.1
  • 068fe24 Merge pull request #8530 from webpack/bugfix/ignore-plugin
  • 6c22ca2 fix issue when contextRegExp is undefined

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 🌴

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

The devDependency webpack was updated from 4.32.2 to 4.33.0.

🚨 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
Release Notes for v4.33.0

Features

  • add target: "electron-preload" for electron 5
    • renderer should use target: "web" in electron 5

Bugfixes

  • fix HMR rejection of removed and readded self-accepted modules
Commits

The new version differs by 21 commits.

  • d45bec3 4.33.0
  • 96869d9 Merge pull request #9191 from webpack/dependabot/npm_and_yarn/chrome-trace-event-1.0.2
  • e90cf7c Merge pull request #9190 from webpack/dependabot/npm_and_yarn/terser-webpack-plugin-1.3.0
  • 96b97b5 Downstream bug fixed and we can remove workaround
  • 31dae4d update snapshots
  • faba6e4 Merge pull request #9209 from webpack/dependabot/npm_and_yarn/@types/node-10.14.8
  • f571d78 Merge pull request #9205 from webpack/dependabot/npm_and_yarn/typescript-3.5.1
  • f59f31d chore(deps-dev): bump @types/node from 10.14.7 to 10.14.8
  • 289c520 chore(deps-dev): bump typescript from 3.4.5 to 3.5.1
  • c408ff5 Merge pull request #9202 from webpack/bugfix/9198
  • 46b428b fix rejection when removing and readding self-accepted module
  • 671cb18 Merge pull request #9188 from kwonoj/electron-preload-target
  • 4345fc5 chore(deps): bump chrome-trace-event from 1.0.0 to 1.0.2
  • 8712474 chore(deps): bump terser-webpack-plugin from 1.2.4 to 1.3.0
  • 2ec75c1 feat(target): support electron preload async chunk loading

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 webpack-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.2.0 to 3.2.1.

🚨 View failing branch.

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

webpack-dev-server 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
Release Notes for v3.2.1

3.2.1 (2019-02-25)

Bug Fixes

  • deprecation message about setup now warning about v4 (#1684) (523a6ec)
  • regression: allow ca, key and cert will be string (#1676) (b8d5c1e)
  • regression: handle key, cert, cacert and pfx in CLI (#1688) (4b2076c)
  • regression: problem with idb-connector after update internal-ip (#1691) (eb48691)
Commits

The new version differs by 9 commits.

  • bf99c26 chore(release): 3.2.1
  • eb48691 fix(regression): problem with idb-connector after update internal-ip (#1691)
  • 4b2076c fix(regression): handle key, cert, cacert and pfx in CLI (#1688)
  • 21687c3 refactor: utils (#1682)
  • 523a6ec fix: deprecation message about setup now warning about v4 (#1684)
  • 884fac0 refactor: remove invalid todo (#1683)
  • a2e5d12 refactor: CLI args and more tests (#1679)
  • 66129a8 test(Util, Validation): close server each time test ends (#1680)
  • b8d5c1e fix: allow ca, key and cert will be string (regression) (#1676)

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 azure-iot-device is breaking the build 🚨

The dependency azure-iot-device was updated from 1.9.3 to 1.9.4.

🚨 View failing branch.

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

azure-iot-device 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
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 azure-iot-device-mqtt is breaking the build 🚨

The dependency azure-iot-device-mqtt was updated from 1.8.1 to 1.8.2.

🚨 View failing branch.

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

azure-iot-device-mqtt 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
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 backend-tslint-rules is breaking the build 🚨

The devDependency backend-tslint-rules was updated from 1.12.0 to 1.12.1.

🚨 View failing branch.

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

backend-tslint-rules 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
Commits

The new version differs by 3 commits.

  • 9a7af07 chore(release): 1.12.1
  • ed8d1dd feat(btr): update curly braces and grouped imports per ASG
  • 76f2337 fix(btr): remove no-inferred-empty-object-type

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

The devDependency azure-iothub was updated from 1.9.5 to 1.9.6.

🚨 View failing branch.

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

azure-iothub 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
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.26.1 to 4.27.0.

🚨 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
Release Notes for v4.27.0

Features

  • When using functions as plugins they are now also called with the compiler as parameter
    • This make it possible to use arrow functions as plugins
  • splitChunks.maxSize now emits a warning when minSize > maxSize
  • Loaders have now access to a getResolve method to create their own resolver function with custom options

Bugfixes

  • splitChunks.cacheGroups.xxx.enforce now behaves as documented and enforce chunk creation
  • splitChunks.cacheGroups.xxx.enforce now no longer deletes minSize for maxSize
  • fixes a bug where splitChunks cause cacheGroups to be incorrectly merged when using the same name
    • now conditions are considered per cacheGroup
    • the correct cache group comment is displayed in stats
  • fixes a bug which causes providedExports not to be updated on rebuilds when using export * from
Commits

The new version differs by 12 commits.

  • f47bf8b 4.27.0
  • a67ffcd Merge pull request #8452 from webpack/feature/resolveWithOptions
  • 96f625c Merge pull request #8457 from webpack/bugfix/rebuild-provided-exports
  • 56feccc convert test case to normal function for node.js 6 support
  • 2f4296e fix a bug which causes incorrect providedExports for cached modules
  • f944002 Merge pull request #8451 from webpack/bugfix/split-chunks
  • 162da1c add getResolve method to loader context
  • 3b46b48 enforce doesn't affect minSize for maxSize
  • 72a8a1f Merge pull request #8440 from Connormiha/oprimize-chunk-can-be-integrated
  • 537d3e4 Cache hasRunstime in chunk
  • e3e8a68 Merge pull request #8405 from xiaoxiaojx/fix-function-plugin-apply
  • 70b9a1b fix parameter missing when plugin type is a funtion

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 @microsoft/applicationinsights-web is breaking the build 🚨

The dependency @microsoft/applicationinsights-web was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

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

@microsoft/applicationinsights-web 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
Release Notes for 2.0.1

trackException Change

This update has a couple of non-breaking API changes. Namely, trackException is now consistent with the Node.js SDK. The only change here is the named argument is renamed from error to exception. A shim is in place so any existing usages of trackException will still work, and the old field is marked as optional, so any type-checked files will still "compile". There are no breaking changes with this change, but you are encouraged to use exception as your named argument field as error will be deprecated in a future major version.

Old

appInsights.trackException({ error: new Error() });

New

appInsights.trackException({ exception: new Error() });

Correlation Header Domain Whitelisting #869

Second, the ability to only send correlation headers to specific, whitelisted domains is now available as a configuration option , correlationHeaderDomains. It accepts an array of domain strings. Wildcards ("*") are okay. By populating this array, all other domains which your application makes requests to will not have correlation headers included. This setting makes it easy to avoid OPTIONS requests to services outside of your control.

You can use the inclusion list and the exclusion list in conjunction with each other to add correlation headers to a particular domain, example.com, and at the same time exclude headers from a prefixed version of it, no-headers.example.com.

Tag Override Change #903

Performing custom tag overrides is now more consistent with all of the other Application Insights SDKs, in that it is modified via a simple key-value dictionary. There are no breaking changes with this update, and if you are setting any tags via the old way, they will still work as they do now. You are encouraged to update them since the old way will be deprecated in a future major version release.

Old

var telemetryInitializer = (item) => {
  item.tags.push({ "ai.cloud.role": "My Web App" });
};
appInsights.addTelemetryInitializer(telemetryInitializer);

New

var telemetryInitializer = (item) => {
  item.tags["ai.cloud.role"] = "My Web App";
};
appInsights.addTelemetryInitializer(telemetryInitializer);

Changelog

#869 - config: add ability to whitelist specific domains for adding correlation headers
#893 - docs: fix sample configuration settings
#899 - common: replace Array.some with Array.forEach to simplify polyfill story, add tests
#902 - snippet: add missing methods to lazy loaders
#903 - tags can now be set with same API as other AI SDKs
#904 - rename IExceptionTelemetry.error --> IExceptionTelemetry.exception
#905 - react: fix plugin causing jest tests to fail
#907 - docs: add mention of how to update current context's operation
#908 - react: remove analytics package dependency
#910 - docs: update context refresh information
#913 - Remove code from adding libVer from extensions
#918 - automatically add ai.operation.name tag, add id to pageview telemetry
#919 - fix issue with namePrefix not affecting send buffers

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.32.1 to 4.32.2.

🚨 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
Release Notes for v4.32.2

Bugfixes

  • fix some weird schema validation messages
  • fix problem in production mode (sideEffects + concatenation) which caused reexported values to become undefined (bug since 4.32.0)
Commits

The new version differs by 10 commits.

  • 5d3004c 4.32.2
  • 689ee4c Merge pull request #9176 from webpack/bugfix/issue-9159
  • fec26a9 fix concatenated version of reexport dependency for sideEffects
  • 6ca9167 Merge pull request #9135 from webpack/dependabot/npm_and_yarn/terser-webpack-plugin-1.2.4
  • 9b368f6 update snapshot
  • 7ccad38 chore(deps): bump terser-webpack-plugin from 1.2.3 to 1.2.4
  • d3ef632 Merge pull request #9167 from webpack/refactor/validation
  • a4406ff improve validation errors
  • 0963d74 add test case for enum validation
  • f1df013 refactor Validation test for snapshots

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 @types/selenium-webdriver is breaking the build 🚨

The devDependency @types/selenium-webdriver was updated from 3.0.14 to 3.0.15.

🚨 View failing branch.

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

@types/selenium-webdriver 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
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 🌴

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 azure-iot-device-mqtt is breaking the build 🚨

The dependency azure-iot-device-mqtt was updated from 1.9.6 to 1.9.7.

🚨 View failing branch.

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

azure-iot-device-mqtt 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
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 azure-iot-device-mqtt is breaking the build 🚨

The dependency azure-iot-device-mqtt was updated from 1.9.9 to 1.10.0.

🚨 View failing branch.

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

azure-iot-device-mqtt 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
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.35.3 to 4.36.0.

🚨 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
Release Notes for v4.36.0

Features

  • SourceMapDevToolPlugin append option now supports the default placeholders in addition to [url]
  • Arrays in resolve and parser options (Rule and Loader API) support backreferences with "..." when overriding options.
Commits

The new version differs by 42 commits.

  • 95d21bb 4.36.0
  • aa1216c Merge pull request #9422 from webpack/feature/dot-dot-dot-merge
  • b3ec775 improve merging of resolve and parsing options
  • 53a5ae2 Merge pull request #9419 from vankop/remove-valid-jsdoc-rule
  • ab75240 Merge pull request #9413 from webpack/dependabot/npm_and_yarn/ajv-6.10.2
  • 0bdabf4 Merge pull request #9418 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-15.5.2
  • f207cdc remove valid jsdoc rule in favour of eslint-plugin-jsdoc
  • 31333a6 chore(deps-dev): bump eslint-plugin-jsdoc from 15.3.9 to 15.5.2
  • 036adf0 Merge pull request #9417 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.8.0
  • 37d4480 Merge pull request #9411 from webpack/dependabot/npm_and_yarn/simple-git-1.121.0
  • ce2a183 chore(deps-dev): bump eslint-plugin-jest from 22.7.2 to 22.8.0
  • 0beeb7e Merge pull request #9391 from vankop/create-hash-typescript
  • bf1a24a #9391 resolve super call discussion
  • bd7d95b #9391 resolve discussions, AbstractMethodError
  • 4190638 chore(deps): bump ajv from 6.10.1 to 6.10.2

There are 42 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 @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 1.5.0 to 1.6.0.

🚨 View failing branch.

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

@typescript-eslint/parser 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
Commits

The new version differs by 12 commits.

  • ab3c1a1 chore: publish v1.6.0
  • a4f95d3 feat(*): change TypeScript version range to >=3.2.1 <3.5.0 (#399)
  • 95a948d chore: initial pull request templates
  • 5d81f8c docs(eslint-plugin): fix markdown format (#394)
  • 492b737 fix(parser): Make eslint traverse enum id (#383)
  • f29d1c9 fix(eslint-plugin): Fix allowExpressions false positives in explicit-function-return-type and incorrect documentation (#388)
  • cebcfe6 fix(eslint-plugin): no-type-alias: fix typeof alias erroring (#380)
  • bf04398 fix(typescript-estree): add ExportDefaultDeclaration to union DeclarationStatement (#378)
  • 643a223 fix(eslint-plugin): explicit-function-return-type: ensure class arrow methods are validated (#377)
  • 6f5c0fa docs(eslint-plugin): list rules requiring type info (#360)
  • ad0f2be fix(eslint-plugin): member-naming false flagging constructors (#376)
  • bea6b92 feat(eslint-plugin): allow explicit variable type with arrow functions (#260)

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

The devDependency azure-iothub was updated from 1.9.6 to 1.9.7.

🚨 View failing branch.

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

azure-iothub 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
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-cli is breaking the build 🚨

The devDependency webpack-cli 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.

webpack-cli 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
Commits

The new version differs by 17 commits.

  • f0031fd chore: v.3.3.2
  • 0309e37 Merge pull request #863 from misterdev/feat/option-to-disable-postinstall
  • c833961 Merge pull request #876 from misterdev/fix-opencollective-eperm
  • b4dfa17 Merge branch 'master' into feat/option-to-disable-postinstall
  • e241b7b chore(docs): Refactors links for badges (#859)
  • 5284b7e fix(opencollective-prompt): check write permissions
  • e17a26d misc(opencollective-prompt): improve grammar
  • 246db42 fix(opencollective prompt): fix grammar
  • d4643ae feat(opencollective prompt): add option to disable it + doc
  • d16404a chore(deps): fix security vulnerabilities (#857)
  • c910463 chore(types): move to @types/yeoman-generator (#869)
  • 68b674b chore(docs): minor fixes in the docs (#874)
  • 7883871 docs: code of conduct (#873)
  • 129a07a chore(travis): removed stable (#871)
  • 309cc1c docs(contribute): adds table of contents and info about dependencies. (#842)

There are 17 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 azure-iot-device is breaking the build 🚨

The dependency azure-iot-device was updated from 1.9.8 to 1.9.9.

🚨 View failing branch.

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

azure-iot-device 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
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 azure-iot-common is breaking the build 🚨

The dependency azure-iot-common was updated from 1.9.6 to 1.9.7.

🚨 View failing branch.

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

azure-iot-common 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
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 azure-iothub is breaking the build 🚨

The devDependency azure-iothub was updated from 1.7.5 to 1.8.0.

🚨 View failing branch.

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

azure-iothub 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
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 @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 1.9.0 to 1.10.0.

🚨 View failing branch.

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

@typescript-eslint/parser 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
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 @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from 24.0.13 to 24.0.14.

🚨 View failing branch.

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

@types/jest 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
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:

🚨 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 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
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 @typescript-eslint/eslint-plugin is breaking the build 🚨

The devDependency @typescript-eslint/eslint-plugin was updated from 1.5.0 to 1.6.0.

🚨 View failing branch.

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

@typescript-eslint/eslint-plugin 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
Commits

The new version differs by 12 commits.

  • ab3c1a1 chore: publish v1.6.0
  • a4f95d3 feat(*): change TypeScript version range to >=3.2.1 <3.5.0 (#399)
  • 95a948d chore: initial pull request templates
  • 5d81f8c docs(eslint-plugin): fix markdown format (#394)
  • 492b737 fix(parser): Make eslint traverse enum id (#383)
  • f29d1c9 fix(eslint-plugin): Fix allowExpressions false positives in explicit-function-return-type and incorrect documentation (#388)
  • cebcfe6 fix(eslint-plugin): no-type-alias: fix typeof alias erroring (#380)
  • bf04398 fix(typescript-estree): add ExportDefaultDeclaration to union DeclarationStatement (#378)
  • 643a223 fix(eslint-plugin): explicit-function-return-type: ensure class arrow methods are validated (#377)
  • 6f5c0fa docs(eslint-plugin): list rules requiring type info (#360)
  • ad0f2be fix(eslint-plugin): member-naming false flagging constructors (#376)
  • bea6b92 feat(eslint-plugin): allow explicit variable type with arrow functions (#260)

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 azure-iot-device is breaking the build 🚨

The dependency azure-iot-device was updated from 1.9.6 to 1.9.7.

🚨 View failing branch.

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

azure-iot-device 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
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.26.0 to 4.26.1.

🚨 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
Release Notes for v4.26.1

Bugfixes

  • fix a bug where splitChunks.maxSize causes a hanging build
  • fix a bug where splitChunks.maxSize crashes when minSize > maxSize
  • fix a edgecase where splitChunks.maxSize can cause chunks bigger than minSize
  • remove unnecessary code from global builtin
Commits

The new version differs by 9 commits.

  • 8e841fe 4.26.1
  • 11afdbd Merge pull request #8417 from webpack/bugfix/split-chunks-min-size
  • cbeaf70 prevent groups with size < minSize
  • a1d4802 Merge pull request #8416 from webpack/bugfix/split-chunks-zero-min
  • 32961f2 while grouping nodes include at least one node on each side
  • fa56ec8 Merge pull request #8410 from webpack/bugfix/max-size-lt-min-size
  • fd2133b handle case when minSize > maxSize
  • 614a6fc Merge pull request #8385 from hax/patch-1
  • 48f0604 Drop unuseful eval call

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 🌴

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.

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.