Coder Social home page Coder Social logo

unional / color-map-rainbow Goto Github PK

View Code? Open in Web Editor NEW
1.0 1.0 0.0 1.77 MB

Creates rainbow of colors

Home Page: https://unional.github.io/color-map-rainbow/

License: MIT License

JavaScript 35.18% TypeScript 64.34% Shell 0.48%
color color-palette rainbow

color-map-rainbow's Issues

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

The devDependency semantic-release was updated from 15.10.5 to 15.10.6.

๐Ÿšจ View failing branch.

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

semantic-release 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).

Release Notes for v15.10.6

15.10.6 (2018-10-27)

Bug Fixes

  • remove dependency to git-url-parse (a99355e)
Commits

The new version differs by 2 commits.

  • a99355e fix: remove dependency to git-url-parse
  • cc06d89 test: fix errors ordering in assertions

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.12.0 to 5.12.1.

๐Ÿšจ View failing branch.

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

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • โœ… coverage/coveralls: First build on greenkeeper/eslint-5.12.1 at 100.0% (Details).

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

The new version differs by 12 commits.

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

See the full diff

FAQ and help

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


Your Greenkeeper Bot ๐ŸŒด

The automated release is failing ๐Ÿšจ

๐Ÿšจ The automated release from the main branch failed. ๐Ÿšจ

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iโ€™m sure you can fix this ๐Ÿ’ช.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those donโ€™t help, or if this issue is reporting something you think isnโ€™t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project โœจ

Your semantic-release bot ๐Ÿ“ฆ๐Ÿš€

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

The devDependency dependency-check was updated from 3.3.0 to 3.3.1.

๐Ÿšจ View failing branch.

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

dependency-check 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).
  • โœ… coverage/coveralls: First build on greenkeeper/dependency-check-3.3.1 at 100.0% (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.12.1 to 5.13.0.

๐Ÿšจ View failing branch.

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

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • โœ… coverage/coveralls: First build on greenkeeper/eslint-5.13.0 at 100.0% (Details).

Release Notes for v5.13.0
  • 91c8884 Chore: use local function to append "s" instead of a package (#11293) (Timo Tijhof)
  • b5143bf Update: for-direction detection false positives/negatives (#11254) (Ruben Bridgewater)
  • 9005e63 Chore: increase camelcase test coverage (#11299) (Redmond Tran)
  • 5b14ad1 Fix: false positive in no-constant-condition (fixes #11306) (#11308) (Pig Fang)
  • 6567c4f Fix: only remove arrow before body in object-shorthand (fixes #11305) (#11307) (Pig Fang)
  • fa2f370 Docs: update rule configuration values in examples (#11323) (Kai Cataldo)
  • 0a3c3ff New: Allow globals to be disabled/configured with strings (fixes #9940) (#11338) (Teddy Katz)
  • dccee63 Chore: avoid hard-coding the list of core rules in eslint:recommended (#11336) (Teddy Katz)
  • c1fd6f5 Chore: remove undocumented Linter#rules property (refs #9161) (#11335) (Teddy Katz)
  • 36e3356 Chore: remove dead code for loading rules (#11334) (Teddy Katz)
  • c464e27 Docs: Rename result -> foo (#11210) (Alexis Tyler)
Commits

The new version differs by 13 commits.

  • 4b267a5 5.13.0
  • 720dce1 Build: changelog update for 5.13.0
  • 91c8884 Chore: use local function to append "s" instead of a package (#11293)
  • b5143bf Update: for-direction detection false positives/negatives (#11254)
  • 9005e63 Chore: increase camelcase test coverage (#11299)
  • 5b14ad1 Fix: false positive in no-constant-condition (fixes #11306) (#11308)
  • 6567c4f Fix: only remove arrow before body in object-shorthand (fixes #11305) (#11307)
  • fa2f370 Docs: update rule configuration values in examples (#11323)
  • 0a3c3ff New: Allow globals to be disabled/configured with strings (fixes #9940) (#11338)
  • dccee63 Chore: avoid hard-coding the list of core rules in eslint:recommended (#11336)
  • c1fd6f5 Chore: remove undocumented Linter#rules property (refs #9161) (#11335)
  • 36e3356 Chore: remove dead code for loading rules (#11334)
  • c464e27 Docs: Rename result -> foo (#11210)

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

Version 5.4.0 of tslint just got published.

Branch Build failing ๐Ÿšจ
Dependency tslint
Current Version 5.3.2
Type devDependency

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

As tslint 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

Release Notes v5.4.0

โญ๏ธ Non-breaking API changes

  • The --type-check CLI option now only enables checking for compiler errors before linting. It is no longer required to enable rules that use the type checker -- only need to supply --project now.

๐ŸŽ‰ New rules, options, and fixers

๐Ÿ›  Bugfixes & enhancements

Thanks to our contributors!

  • Klaus Meinhardt
  • Manuel Lopez
  • Andy Hanson
  • Piotr Tomiak
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 semantic-release is breaking the build ๐Ÿšจ

The devDependency semantic-release was updated from 15.13.15 to 15.13.16.

๐Ÿšจ View failing branch.

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

semantic-release 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).
  • โœ… coverage/coveralls: First build on greenkeeper/semantic-release-15.13.16 at 100.0% (Details).

Release Notes for v15.13.16

15.13.16 (2019-06-07)

Bug Fixes

  • package: update env-ci to version 4.0.0 (8051294)
Commits

The new version differs by 3 commits.

  • 4ed6213 style: fix prettier style
  • 8051294 fix(package): update env-ci to version 4.0.0
  • 95a0456 chore(package): update ava to version 2.0.0

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

The devDependency rollup was updated from 1.1.0 to 1.1.1.

๐Ÿšจ View failing branch.

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

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • โœ… coverage/coveralls: First build on greenkeeper/rollup-1.1.1 at 100.0% (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 ava is breaking the build ๐Ÿšจ

The devDependency ava was updated from 1.1.0 to 1.2.0.

๐Ÿšจ View failing branch.

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

ava 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).

Release Notes for 1.2.0

New features

You can now set a timeout for test themselves. The test will fail if this timeout is exceeded. The timeout is reset each time an assertion is made:

test('foo', t => {
	t.timeout(100); // 100 milliseconds
	// Write your assertions here
});

b65c6d7

AVA also has a global timeout feature. The mini reporter now logs tests that were pending when those timeouts occur. Additionally, if you interrupt a test using ctrl+c we'll now also show the pending tests. 2b60556

Thank you @dflupu for your hard work on this!

Bug fixes and other improvements

  • We're no longer truncating multi-line error messages 72e0762
  • Unexpected errors in the throws assertions are now reported with the correct stack trace ad087f2
  • The Debugging with VSCode recipe has been updated with the correct workspaceFolder variable 0a5fe42 and --serial argument placement edfc005

All changes ๐Ÿ“š

v1.1.0...v1.2.0

Thanks ๐Ÿ’Œ

๐Ÿ’– Huge thanks to @anishkny, @CrispusDH, @dflupu and @niktekusho for helping us with this release. We couldnโ€™t have done it without you!

Get involved โœŒ๏ธ

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

Commits

The new version differs by 11 commits.

  • 010914b 1.2.0
  • ad087f2 Fix stack traces in throw assertions
  • 8ad5efd Bump dependencies
  • 2b60556 Print pending tests on interrupt, and on timeout in mini reporter
  • 0a5fe42 Change deprecated workspaceRoot variable to the equivalent workspaceFolder
  • b65c6d7 Add t.timeout()
  • ed7807e Linter fixes
  • f0a07cd Rely on npm 6.6.0
  • 6b10f2e Bump XO and fix some lint issues
  • 72e0762 Fix accidental truncation of multi-line error messages
  • edfc005 Fix profile.js example

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

The devDependency ava was updated from 1.0.1 to 1.1.0.

๐Ÿšจ View failing branch.

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

ava 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).
  • โœ… coverage/coveralls: First build on greenkeeper/ava-1.1.0 at 100.0% (Details).

Release Notes for 1.1.0

1.1.0

New features

AVA now exports a meta object. Currently, you can retrieve the path of the test file being run:

import test from 'ava';

console.log('Test currently being run: ', test.meta.file);

import {meta} from 'ava';

console.log('Test currently being run: ', meta.file);

This is useful in helpers that need to know the test file. bccd297

Bug fixes and other improvements

  • t.log() now works in hooks d187712

  • Error output for improper usage of t.throws() once again links to the correct documentation dc552bc

  • We've added a section on webpack aliases to the Babel recipe c3bcbf2

  • We've updated the Vue recipe for Babel 7, and added a section on webpack aliases c3bcbf2

All changes ๐Ÿ“š

v1.0.1...v1.1.0

Thanks ๐Ÿ’Œ

๐Ÿ’– Huge thanks to @fitztrev, @forresst, @astrob0t, @pearofducks, @coreyfarrell and @dflupu for helping us with this release. We couldnโ€™t have done it without you!

Get involved โœŒ๏ธ

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

Commits

The new version differs by 9 commits.

  • a28094a 1.1.0
  • 7262a78 Bump dependencies
  • d187712 Fix t.log() in hooks
  • bccd297 Expose test file path within worker process
  • c3bcbf2 Improve Babel and Vue recipes
  • dc552bc Update link to t.throws() assertion in AVA output
  • f4b2d19 Fix links to French translation of docs (#2005)
  • 2e72fe7 Fix npm install command in readme (#2001)
  • 7b6e578 Use newer ES syntax where possible

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

The devDependency rollup-plugin-commonjs was updated from 9.2.0 to 9.2.1.

๐Ÿšจ View failing branch.

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

rollup-plugin-commonjs 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).
  • โœ… coverage/coveralls: First build on greenkeeper/rollup-plugin-commonjs-9.2.1 at 100.0% (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 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).
  • โœ… coverage/coveralls: First build on greenkeeper/rimraf-2.6.3 at 100.0% (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 ๐ŸŒด

Dependency Dashboard

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

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • chore(deps): update dependency pascal-case to v4
  • chore(deps): update dependency rollup to v4
  • chore(deps): update dependency size-limit to v11
  • chore(deps): update dependency typedoc-plugin-extras to v3
  • chore(deps): update github/codeql-action action to v3
  • ๐Ÿ” Create all rate-limited PRs at once ๐Ÿ”

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

Open

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

Detected dependencies

github-actions
.github/workflows/codeql-analysis.yml
  • actions/checkout v4
  • github/codeql-action v2
  • github/codeql-action v2
  • github/codeql-action v2
.github/workflows/nodejs.yml
npm
package.json
  • color-map ^1.1.0
  • @babel/core ^7.17.9
  • @babel/preset-env ^7.16.11
  • @babel/preset-typescript ^7.16.7
  • @commitlint/cli ^19.0.0
  • @commitlint/config-conventional ^19.0.0
  • @size-limit/preset-small-lib ^9.0.0
  • @types/jest ^28.0.0
  • @typescript-eslint/eslint-plugin ^5.23.0
  • ansi-styles 5
  • depcheck ^1.4.3
  • eslint ^8.14.0
  • eslint-plugin-harmony ^7.0.2
  • husky ^8.0.0
  • jest ^28.0.0
  • jest-validate ^28.0.0
  • jest-watch-suspend ^1.1.2
  • jest-watch-toggle-config ^2.0.1
  • jest-watch-typeahead ^2.0.0
  • npm-run-all2 ^6.0.0
  • param-case ^2.1.1
  • pascal-case ^2.0.1
  • rimraf ^5.0.0
  • rollup ^2.4.0
  • rollup-plugin-commonjs ^10.0.0
  • rollup-plugin-node-builtins ^2.1.2
  • rollup-plugin-node-globals ^1.4.0
  • rollup-plugin-node-resolve ^5.0.0
  • rollup-plugin-sourcemaps ^0.6.0
  • size-limit ^8.0.0
  • ts-loader ^9.0.0
  • typedoc ^0.25.0
  • typedoc-plugin-extras ^2.2.3
  • typescript ^4.6.3
  • webpack ^5.0.0
  • webpack-cli ^5.0.0

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

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

The devDependency webpack was updated from 4.20.2 to 4.21.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
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.21.0

Features

  • add output.libraryTarget: "amd-require" which generates a AMD require([], ...) wrapper instead of a define([], ...) wrapper
  • support arrays of strings passed to output.library, which exposes the library to a subproperty

Bugfixes

  • fix cases where __webpack_require__.e is used at runtime but is not defined in the bundle
  • fix behavior of externals of global type

Performance

  • Some performance improvements to the chunk graph generation
Commits

The new version differs by 37 commits.

  • 432d2a3 4.21.0
  • 0fb6c60 Merge pull request #7038 from marcusdarmstrong/marcusdarmstrong-external-module-fix
  • 15b6f8b make afterEach async
  • 7bc5c98 Merge branch 'master' into marcusdarmstrong-external-module-fix
  • 2228daf Merge pull request #8230 from webpack/revert-8120-rh-silent-reporter
  • fadf875 remove dependency
  • 7c0b209 Revert "Re-enable jest-silent-reporter #hacktoberfest"
  • a868789 Merge pull request #8143 from MLoughry/miclo/optimize-chunk-graph-generation
  • 1d71ede Make changes suggested by @sokra to optimize chunk graph generation
  • 4d3fe00 Merge pull request #8134 from fscherwi/update-coveralls
  • 86f56bf update coveralls
  • 4c461e2 Merge pull request #8120 from rickhanlonii/rh-silent-reporter
  • 9fe42e7 Merge pull request #8118 from webpack/bugfix/issue-8110
  • 0b6ad2a Don't be clever with the set command because idk windows
  • 148016e Rerun yarn

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

The automated release is failing ๐Ÿšจ

๐Ÿšจ The automated release from the master branch failed. ๐Ÿšจ

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iโ€™m sure you can resolve this ๐Ÿ’ช.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those donโ€™t help, or if this issue is reporting something you think isnโ€™t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project โœจ

Your semantic-release bot ๐Ÿ“ฆ๐Ÿš€

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

The devDependency nyc was updated from 13.1.0 to 13.2.0.

๐Ÿšจ View failing branch.

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

nyc 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).
  • โœ… coverage/coveralls: First build on greenkeeper/nyc-13.2.0 at 100.0% (Details).

Commits

The new version differs by 17 commits.

  • 29e6f5e chore(release): 13.2.0
  • e95856c chore: Update dependencies. (#978)
  • 921d386 fix: Create directory for merge destination. (#979)
  • df2730d feat: Option Plugins (#948)
  • 35cd49a feat: document the fact that cacheDir is configurable (#968)
  • ff834aa feat: avoid hardcoded HOME for spawn-wrap working dir (#957)
  • 35710b1 build: move windows tests to travis (#961)
  • 93cb5c1 tests: coverage for temp-dir changes (#964)
  • d566efe test: stop using LAZY_LOAD_COUNT (#960)
  • f23d474 chore: update stale bot config with feedback (#958)
  • 62d7fb8 chore: slight tweak to position of test
  • 28b6d09 fix: missing command temp-directory (#928)
  • 40afc5f fix: nyc processing files not covered by include when all is enabled. (#914)
  • ba22a26 docs(readme): Update to reflect .nycrc.json support (#934)
  • 2dbb82d chore: enable probot-stale

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

The devDependency dependency-check 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.

dependency-check 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).

Commits

The new version differs by 4 commits.

  • 32c1b74 3.3.0
  • e3ff1df update travis setup with new node versions
  • 3f302e0 Clarifies that --ignore-module works for unused and missing
  • 5aff1bc Silently pass on unsupported versions of Node.js

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

The devDependency rollup-plugin-node-resolve was updated from 4.0.0 to 4.0.1.

๐Ÿšจ View failing branch.

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

rollup-plugin-node-resolve 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).

Commits

The new version differs by 5 commits.

  • f8dfa57 4.0.1
  • 2ba2515 Update changelog
  • 1eff8d7 fix: regression in browser objects pointing to nested node_mpodules (#143)
  • aad0239 Update changelog
  • 9ce01d4 Fix pkg.browser mappings issue by specifying a value of false (#183)

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

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! ๐ŸŽŠ

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

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

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

More information on this issue

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

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

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


FAQ and help

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


Your Greenkeeper Bot ๐ŸŒด

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

The devDependency rollup was updated from 1.0.0 to 1.0.1.

๐Ÿšจ View failing branch.

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

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • โœ… coverage/coveralls: First build on greenkeeper/rollup-1.0.1 at 100.0% (Details).

Release Notes for v1.0.1

2019-01-03

Bug Fixes

  • Properly handle reexporting an external default export for non-ESM targets when using named exports mode (#2620)
  • Do not (wrongly) re-declare input options in the merged RollupOptions type (#2622)

Pull Requests

Commits

The new version differs by 6 commits.

  • fbb5f9e 1.0.1
  • e7b3c78 Update changelog
  • eda15fa Update changelog
  • 5ff6352 Show how to skip imports for optional plugins (#2627)
  • 6d32530 Simplify RollupOptions (#2622)
  • f5364d9 Fixed issue with reexporting default as default with {exports: named, interop: true} options. (#2620)

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

Release Notes for v4.29.0

Features

  • update acorn to v6
  • limit the number of in parallel written output files to 15
  • add output.futureEmitAssets which gives the emitting logic of webpack 5
    • assets are replaced with SizeOnlySources
    • reading assets after emitting is no longer allowed
    • This allows memory to be garbage-collected
Commits

The new version differs by 10 commits.

  • 25bccd4 4.29.0
  • 6389e41 Merge pull request #8642 from webpack/memory/future-emit-assets
  • 6e383cf make test for Source.buffer more strict
  • aaf85db add output.futureEmitAssets
  • 03ffa48 Merge pull request #8639 from webpack/memory/limit-parallelism
  • 2b2c17f Merge pull request #8598 from kiliancs/acorn6
  • 80514cc Add ts declarations
  • 78abf04 Use eachLimit instead even though forEachLimit apears to be an alias...
  • 9cb4225 forEach to forEachLimit
  • ef67132 Upgrade acorn to v6

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.