Giter VIP home page Giter VIP logo

q-infographic's People

Contributors

benib avatar fromdusttilldawn avatar greenkeeper[bot] avatar manuelroth avatar migingreen avatar philipkueng avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

q-infographic's Issues

Serve lossy webp if new option `serveLosslessWebP` is not checked

Current

We serve lossless WebP allways: https://github.com/nzzdev/Q-infographic/blob/dev/helpers/images.js#L71-L72

Should

  • Add new option serveLosslessWebP defaulting to false
  • Serve images with lossy WebP: change webpll to webply for the fastly parameter
  • Only if the option serveLosslessWebP is true, serve webpll

This does not need any migration for existing graphics. If one finds one that has problems with lossy, one can enable the option.

An in-range update of uglify-js is breaking the build 🚨

The dependency uglify-js was updated from 3.6.1 to 3.6.2.

🚨 View failing branch.

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

uglify-js 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 v3.6.2

 

Commits

The new version differs by 9 commits.

  • c3ca293 v3.6.2
  • 516b67a minor tweaks to CI test scripts (#3467)
  • eba3a37 fix boolean context detection (#3466)
  • 6d57ca1 improve source map handling (#3464)
  • 3320251 update benchmark URLs (#3462)
  • 33c94d3 detect boolean context across IIFEs (#3461)
  • b18f717 improve readability of --help ast (#3460)
  • a0d4b64 remove extraneous property (#3459)
  • 6db880e clean up AST_Binary optimisation logic (#3458)

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 @hapi/inert is breaking the build 🚨

The dependency @hapi/inert was updated from 5.2.1 to 5.2.2.

🚨 View failing branch.

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

@hapi/inert 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 7 commits.

  • 9c08c72 5.2.2
  • 05d2784 Update joi. Closes #130
  • 3a1d137 Merge pull request #124 from zimokha/broken-links
  • 8b20992 Update deps
  • 4492bc5 adding slash for top level if path does not end with slash
  • 6e76104 make readable comment
  • e731098 fixing broken links in directory listing

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

The dependency @hapi/hapi was updated from 18.3.2 to 18.4.0.

🚨 View failing branch.

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

@hapi/hapi 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 30 commits.

There are 30 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 🌴

Adjust dynamicEnum and availabilityChecks to new configuration format

Task

We made changes to the configuration format of dynamicEnums and availabilityChecks. The schema and corresponding routes need to be adjusted as following (more details on the config format can be found here):

DynamicEnums

Current:

"dynamicEnum": {
  "type": "ToolEndpoint",
  "withData": true,
  "endpoint": "dynamic-enum/selectedColumn"
}

New:

"dynamicEnum": {
  "type": "ToolEndpoint",
  "config": {
    "endpoint": "dynamic-enum/selectedColumn",
    "fields": ["options", "data"]
  }
}

Additionally the /dynamic-enum now receives an object containing the item and optionally and options property. The route needs to be adjusted to this.

AvailabilityChecks

Current:

{
  "type": "ToolEndpoint",
  "withData": true,
  "endpoint": "option-availability/invertColors"
}

New:

{
  "type": "ToolEndpoint",
  "config": {
    "endpoint": "option-availability/invertColors",
    "data": ["options", "data"]
  } 
}

Additionally the /option-availability now receives an object containing the item and optionally and options property. The route needs to be adjusted to this.

Action required: Greenkeeper could not be activated 🚨


🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io


🚨 You need to enable Continuous Integration on Greenkeeper 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:

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 click the 'fix repo' button on account.greenkeeper.io.

An in-range update of amphtml-validator is breaking the build 🚨

The devDependency amphtml-validator was updated from 1.0.23 to 1.0.24.

🚨 View failing branch.

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

amphtml-validator 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 🌴

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.