Git Product home page Git Product logo

djangocms-equation's Introduction

djangocms-equation

PyPi Version Supported Python Versions License

Test Status Documentation Status Code Coverage Docstring Coverage This project is using Percy.io for visual regression testing.

Codacy code quality Total alerts Language grade: Python Language grade: JavaScript

Dependabot Status Code style Python: black Code style TypeScript: prettier

DjangoCMS plugin to write equations, utilizing KaTeX

Features

  • Enables the use of LaTeX for equations with django-cms
  • Live editing of LaTeX Code, via KaTeX
  • Out of the box support for mhchem
  • Configurable allowing of copying of equation LaTeX code

Installation

Install the plugin from PyPi

$ pip install djangocms-equation

Add the plugin to the installed apps in the settings.py of your django-cms project.

"INSTALLED_APPS": [..., "djangocms_equation"]

For the Equations to be properly displayed in djangocms-text-ckeditor, while edit them, you need to add the css file to the allowed files of ckeditor. To do this simply add the following lines to your settings.py of your django-cms project.

CKEDITOR_SETTINGS = {
    "contentsCss": ["/static/djangocms_equation/css/change_form_template.css"]
}

Note:

The equations might not be rendered properly in ckeditor-windows, when they are added the first time. This can be fixed by saving the text plugin or having another equation on the page.

To allow copying of equations LaTeX code, add the following line to your settings.py.

"KATEX_EQUATION_SETTINGS" = {"allow_copy": True}

Credits

This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.

djangocms-equation's People

Contributors

dependabot-preview[bot] avatar dependabot[bot] avatar greenkeeper[bot] avatar pyup-bot avatar s-weigand avatar

Stargazers

avatar avatar avatar avatar

Watchers

avatar avatar avatar

Forkers

lgtm-migrator

djangocms-equation's Issues

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

The devDependency @types/node was updated from 12.7.3 to 12.7.4.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.4 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.0.0 to 12.0.1.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (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 less is breaking the build 🚨

The devDependency less was updated from 3.10.2 to 3.10.3.

🚨 View failing branch.

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

less 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.7.4 to 12.7.5.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.5 at 100.0% (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (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 12.7.12 to 12.11.0.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.11.0 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.11.5 to 12.11.6.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.11.6 at 99.918% (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 12.7.9 to 12.7.10.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.10 at 99.918% (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 11.13.2 to 11.13.3.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (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 katex is breaking the build 🚨

The dependency katex was updated from 0.11.0 to 0.11.1.

🚨 View failing branch.

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

katex 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/katex-0.11.1 at 98.718% (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 12.11.7 to 12.12.0.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.12.0 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.7.8 to 12.7.9.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.9 at 99.888% (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 sass is breaking the build 🚨

The devDependency sass was updated from 1.23.3 to 1.23.5.

🚨 View failing branch.

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

sass 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/sass-1.23.5 at 98.765% (Details).
Release Notes for Dart Sass 1.23.5

To install Dart Sass 1.23.5, download one of the packages above and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • Support inline comments in the indented syntax.

  • When an overloaded function receives the wrong number of arguments, guess which overload the user actually meant to invoke, and display the invalid argument error for that overload.

  • When @error is used in a function or mixin, print the call site rather than the location of the @error itself to better match the behavior of calling a built-in function that throws an error.

See the full changelog for changes in earlier releases.

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

The devDependency sass was updated from 1.18.0 to 1.19.0.

🚨 View failing branch.

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

sass 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for Dart Sass 1.19.0

To install Dart Sass 1.19.0, download one of the packages above and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • Allow ! in url()s without quotes.

Dart API

  • FilesystemImporter now doesn't change its effective directory if the working directory changes, even if it's passed a relative argument.

See the full changelog for changes in earlier releases.

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

The devDependency @types/katex was updated from 0.10.1 to 0.10.2.

🚨 View failing branch.

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

@types/katex 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/katex-0.10.2 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 sass is breaking the build 🚨

The devDependency sass was updated from 1.23.0 to 1.23.1.

🚨 View failing branch.

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

sass 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/sass-1.23.1 at 99.897% (Details).
Release Notes for Dart Sass 1.23.1

To install Dart Sass 1.23.1, download one of the packages above and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • Fix a bug preventing built-in modules from being loaded within a configured module.

  • Fix a bug preventing an unconfigured module from being loaded from within two different configured modules.

  • Fix a bug when meta.load-css() was used to load some files that included media queries.

  • Allow saturate() in plain CSS files, since it can be used as a plain CSS filter function.

  • Improve the error messages for trying to access functions like lighten() from the sass:color module.

See the full changelog for changes in earlier releases.

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 12.7.11 to 12.7.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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.12 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 sass is breaking the build 🚨

The devDependency sass was updated from 1.22.7 to 1.22.8.

🚨 View failing branch.

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

sass 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for Dart Sass 1.22.8

To install Dart Sass 1.22.8, download one of the packages above and add it to your PATH, or see the Sass website for full installation instructions.

Changes

JavaScript API

  • Don't crash when running in a directory whose name contains URL-sensitive characters.

  • Drop support for Node Carbon (8.x), which doesn't support url.pathToFileURL.

See the full changelog for changes in earlier releases.

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 🌴

Update to django3.2, djangocms3.9 and ckeditor4.0

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

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

The devDependency @types/node was updated from 12.12.7 to 12.12.8.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.12.8 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 sass is breaking the build 🚨

The devDependency sass was updated from 1.22.12 to 1.23.0.

🚨 View failing branch.

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

sass 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/sass-1.23.0 at 100.0% (Details).
Release Notes for Dart Sass 1.23.0

To install Dart Sass 1.23.0, download one of the packages above and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • Launch the new Sass module system! This adds:

    • The @use rule, which loads Sass files as modules and makes their members available only in the current file, with automatic namespacing.

    • The @forward rule, which makes members of another Sass file available to stylesheets that @use the current file.

    • Built-in modules named sass:color, sass:list, sass:map, sass:math, sass:meta, sass:selector, and sass:string that provide access to all the built-in Sass functions you know and love, with automatic module namespaces.

    • The [meta.load-css() mixin][], which includes the CSS contents of a module loaded from a (potentially dynamic) URL.

    • The meta.module-variables() function, which provides access to the variables defined in a given module.

    • The meta.module-functions() function, which provides access to the functions defined in a given module.

    Check out [the Sass blog][migrator blog] for more information on the new module system. You can also use the new [Sass migrator][] to automatically migrate your stylesheets to the new module system!

    [migrator blog]: https://sass-lang.com/blog/7858341-the-module-system-is-launched [Sass migrator]: https://sass-lang.com/documentation/cli/migrator

See the full changelog for changes in earlier releases.

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 12.7.7 to 12.7.8.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.8 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.6.9 to 12.7.0.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.0 at 93.59% (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 12.7.5 to 12.7.6.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.6 at 98.718% (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (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 parcel is breaking the build 🚨

The devDependency parcel was updated from 1.12.3 to 1.12.4.

🚨 View failing branch.

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

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

The devDependency @types/node was updated from 12.12.8 to 12.12.9.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.12.9 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.11.4 to 12.11.5.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.11.5 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.7.0 to 12.7.1.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.1 at 93.59% (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 12.11.6 to 12.11.7.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.11.7 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.7.1 to 12.7.2.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.7.2 at 100.0% (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (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 12.12.9 to 12.12.10.

🚨 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/@types/node-12.12.10 at 99.559% (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 sass is breaking the build 🚨

The devDependency sass was updated from 1.19.0 to 1.20.1.

🚨 View failing branch.

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

sass 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
  • ✅ pyup.io/safety-ci: No dependencies with known security vulnerabilities. (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for Dart Sass 1.20.1

To install Dart Sass 1.20.1, download one of the packages above and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • No user-visible changes.

See the full changelog for changes in earlier releases.

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 🌴

Make percy work again

Atm Percy is broken due to the change to github actions.
Like for other service clients this might also be due to the client no yet being compatible with gh-actions.

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.