unional / color-map Goto Github PK

View Code? Open in Web Editor NEW

13.0 13.0 3.0 9.33 MB

Color map generator

License: MIT License

JavaScript 20.79% TypeScript 74.08% HTML 2.31% Shell 2.82%

color color-palette

color-map's People

Contributors

Stargazers

Watchers

Forkers

jack-hf graydalf solaryasha

color-map's Issues

An in-range update of @unional/devpkg-node is breaking the build 🚨

The devDependency @unional/devpkg-node 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.

@unional/devpkg-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

❌ all: * node-latest - Failed

node8 - Blocked
node6 - Blocked
node10 - Blocked
node9 - Blocked

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

❌ all: * node-latest - Failed

node9 - Blocked
node10 - Blocked
node8 - Blocked
node6 - Blocked

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 🌴

Dependency Dashboard

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

Open

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

Detected dependencies

github-actions

.github/workflows/codeql-analysis.yml

actions/checkout v4

github/codeql-action v3

github/codeql-action v3

github/codeql-action v3

.github/workflows/pull-request.yml

.github/workflows/release.yml

npm

package.json

@commitlint/cli ^18.0.0

@commitlint/config-conventional ^18.0.0

@repobuddy/jest ^3.0.0

@semantic-release/changelog ^6.0.1

@semantic-release/git ^10.0.1

@semantic-release/github ^9.0.0

@semantic-release/npm ^11.0.0

@size-limit/preset-small-lib ^9.0.0

@types/jest ^29.0.0

@typescript-eslint/eslint-plugin ^5.27.1

assertron ^11.0.0

depcheck ^1.4.3

eslint ^8.17.0

eslint-plugin-harmony ^7.1.0

husky ^8.0.1

jest ^29.0.0

jest-junit ^16.0.0

jest-progress-tracker ^3.0.4

jest-validate ^29.0.0

jest-watch-repeat ^3.0.0

jest-watch-suspend ^1.1.2

jest-watch-toggle-config-2 ^2.1.0

jest-watch-typeahead ^2.0.0

ncp ^2.0.0

npm-run-all ^4.1.5

param-case ^3.0.4

pascal-case ^3.1.2

pinst ^3.0.0

rimraf ^5.0.0

semantic-release ^22.0.0

size-limit ^9.0.0

ts-jest ^29.0.0

ts-loader ^9.3.0

tslib ^2.4.0

typescript ^5.0.0

webpack ^5.73.0

webpack-cli ^5.0.0

yarn 3.7.0

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

An in-range update of source-map-loader is breaking the build 🚨

Version 0.2.2 of source-map-loader just got published.

Branch	Build failing 🚨
Dependency	source-map-loader
Current Version	0.2.1
Type	devDependency

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

As source-map-loader 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

✅ coverage/coveralls First build on greenkeeper/source-map-loader-0.2.2 at 100.0% Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

Release v0.2.2

0.2.2 (2017-09-30)

Bug Fixes

Handle exception on loading invalid base64 source maps (#53) (38da2eb)

Commits

The new version differs by 5 commits.

fdcfea6 chore(release): 0.2.2
38da2eb fix: Handle exception on loading invalid base64 source maps (#53)
e0bff76 docs(README): define more precisely what loader does (#47)
54ee6ea Remove plus signs from copy. (#44)
5501fe3 docs(README): add details on usage and purpose (#37)

See the full diff

Not sure how things should work exactly?

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

Your Greenkeeper Bot 🌴

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

The devDependency webpack-cli was updated from `3.2.3` 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-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

✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
✅ coverage/coveralls: First build on greenkeeper/webpack-cli-3.3.0 at 100.0% (Details).
❌ all: * node-latest - Failed

node9 - Blocked
node8 - Blocked
node6 - Blocked
node10 - Blocked

Commits

The new version differs by 114 commits ahead by 114, behind by 82.

8955506 chore: v.3.3.0
398e39a Merge pull request #773 from misterdev/misterdev-format-scaffold
a14908e chore: revise typo
d19c1f7 docs(scaffolding): lowercase Webpack
b94b0de docs(scaffolding): fix typos
6b79072 docs(scaffolding): improve grammar
65bf27f docs: add lerna badge in README (#786)
98818a1 docs(scaffolding): fix typo
0f657d0 docs(scaffolding): improve description & formatting
6aec4c3 Merge pull request #742 from rishabh3112/fix/init
e2c9dd7 Merge pull request #768 from misterdev/docs/contributing-formatting
6fee805 Merge pull request #785 from webpack/fix/ci
a8b46bf chore(deps): @std/esm -> esm
54a3ac4 fix(tests): remove snapshot for static compilation
3af0948 fix(tests): remove snapshot for static compilation

There are 114 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 nyc is breaking the build 🚨

Version 11.3.0 of nyc was just published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.2.1
Type	devDependency

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 could not complete due to an error Details

Commits

The new version differs by 12 commits.

d85118c chore(release): 11.3.0
7792733 chore: explicitly update istanbul dependencies (#698)
222a3d0 chore: slight difference in pinning logic, based on @ljharb's advice
f04b7a9 feat: add option to hook vm.runInContext (#680)
cdfdff3 feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
a413f6a chore: upgrade to yargs 10 (#694)
10125aa docs: fix reporters link
f5089ca docs: added examples of coverage reports (#656)
af281e7 chore: update spawn-wrap to 1.4.0 (#692)
a685f7c docs: missing options prefix -- in front of check-coverage (#695)
f31d7a6 feat: allow instrument-only to produce sourcemaps (#674)
425c0fd chore: ignore package-lock.json (#683)

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

Version 2.3.0 of colormap just got published.

Branch	Build failing 🚨
Dependency	colormap
Current Version	2.2.0
Type	devDependency

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

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

✅ coverage/coveralls First build on greenkeeper/colormap-2.3.0 at 100.0% Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 14 commits.

286c112 Merge pull request #15 from bpostlethwaite/updates
48d23d9 Version bump
e04cdee Fix review
31a05ae Make readme more concise
61232dd Fix tests
26dcc74 Update readme
659ce8e Remove unused deps
3bf8d0e Update readme
2f1fe00 Smoothen maps, get rid of double colors
ba79a78 Refactor inner logic, avoid doubly colors
dc1436d Fresh up test dep
40d0100 Add readme markers
cbfb117 Merge pull request #11 from substack/alpha-index
281a38e second alpha index should be 1, not 0

See the full diff

Not sure how things should work exactly?

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

Your Greenkeeper Bot 🌴

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
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

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 🌴

clarify the behavior of `createColorsFromMap()`

e.g.:

export function createColorsFromMap(colormap: ColorMap, shades: number): RGB[]
export function createColorsFromMap(colormap: ColorMap | ColorMapAlpha, shades: number, alpha: Alpha): RGBA[]
export function createColorsFromMap(colormap: ColorMapAlpha, shades: number): RGBA[]

But even that is not sufficient. What if:

createColorsFromMap([{ index: 0, rgb: [0,0,0] }, { index: 1, rgb: [1,1,1,1] }], 2, [0.1, 0.8])

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

Version 4.8.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.7.2
Type	devDependency

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

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

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ coverage/coveralls First build on greenkeeper/eslint-4.8.0 at 100.0% Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v4.8.0

3f2b908 New: add option to report unused eslint-disable directives (fixes #9249) (#9250) (Teddy Katz)
ff2be59 Fix: dot notation rule failing to catch string template (fixes #9350) (#9357) (Phil Quinn)
b1372da Chore: remove sourceCode property from Linter (refs #9161) (#9363) (Teddy Katz)
cef6f8c Docs: remove line about removing rules from semver policy (#9367) (Teddy Katz)
06efe87 Fix: Add meta element with charset attribute. (#9365) (H1Gdev)
458ca67 Docs: update architecture page (fixes #9337) (#9345) (Victor Hom)
1c6bc67 Fix: special EventEmitter keys leak information about other rules (#9328) (Teddy Katz)
d593e61 Docs: update eslint.org links to use https (#9358) (Teddy Katz)
38d0cb2 Fix: fix wrong code-path about try-for-in (fixes #8848) (#9348) (Toru Nagashima)
434d9e2 Fix: Invalid font-size property value issue. (#9341) (H1Gdev)
a7668c2 Chore: Remove unnecessary slice from logging utility (#9343) (Gyandeep Singh)
2ff6fb6 Chore: remove unused arguments in codebase (#9340) (Teddy Katz)

Commits

The new version differs by 14 commits.

8ebb034 4.8.0
916a2d7 Build: changelog update for 4.8.0
3f2b908 New: add option to report unused eslint-disable directives (fixes #9249) (#9250)
ff2be59 Fix: dot notation rule failing to catch string template (fixes #9350) (#9357)
b1372da Chore: remove sourceCode property from Linter (refs #9161) (#9363)
cef6f8c Docs: remove line about removing rules from semver policy (#9367)
06efe87 Fix: Add meta element with charset attribute. (#9365)
458ca67 Docs: update architecture page (fixes #9337) (#9345)
1c6bc67 Fix: special EventEmitter keys leak information about other rules (#9328)
d593e61 Docs: update eslint.org links to use https (#9358)
38d0cb2 Fix: fix wrong code-path about try-for-in (fixes #8848) (#9348)
434d9e2 Fix: Invalid font-size property value issue. (#9341)
a7668c2 Chore: Remove unnecessary slice from logging utility (#9343)
2ff6fb6 Chore: remove unused arguments in codebase (#9340)

See the full diff

Not sure how things should work exactly?

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

Your Greenkeeper Bot 🌴

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

The devDependency eslint was updated from `5.12.0` to `5.12.1`.

🚨 View failing branch.

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

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

Status Details

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

An in-range update of @unional/devpkg-node is breaking the build 🚨

The devDependency @unional/devpkg-node was updated from `1.3.2` to `1.3.3`.

🚨 View failing branch.

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

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
❌ all: * node-latest - Failed

node8 - Blocked
node6 - Blocked
node10 - Blocked
node9 - Blocked

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 to 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 📦🚀

unional / color-map Goto Github PK

color-map's People

Contributors

Stargazers

Watchers

Forkers

color-map's Issues

The devDependency @unional/devpkg-node was updated from 1.4.1 to 1.4.2.

The devDependency webpack was updated from 4.35.3 to 4.36.0.

Features

Open

Detected dependencies

Version 0.2.2 of source-map-loader just got published.

0.2.2 (2017-09-30)

Bug Fixes

The devDependency webpack-cli was updated from 3.2.3 to 3.3.0.

Version 11.3.0 of nyc was just published.

Version 2.3.0 of colormap just got published.

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

Version 4.8.0 of eslint just got published.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

The devDependency eslint was updated from 5.12.0 to 5.12.1.

The devDependency @unional/devpkg-node was updated from 1.3.2 to 1.3.3.

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency @unional/devpkg-node was updated from `1.4.1` to `1.4.2`.

The devDependency webpack was updated from `4.35.3` to `4.36.0`.

The devDependency webpack-cli was updated from `3.2.3` to `3.3.0`.

🚨 The automated release from the `master` branch failed. 🚨

The devDependency eslint was updated from `5.12.0` to `5.12.1`.

The devDependency @unional/devpkg-node was updated from `1.3.2` to `1.3.3`.

🚨 The automated release from the `master` branch failed. 🚨