Giter VIP home page Giter VIP logo

reframe.js's Introduction

⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️

This software is maintained under a new repository located at yowainwright/reframe.js

⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️


Reframe.js, reframe your content responsively

npm version 0.3.6 unpkg Greenkeeper Build Status Share


🖼 Reframe.js

Reframe.js is a javascript plugin that makes elements scale at a fixed ratio.

This is particularly awesome for making embedded stuff, like videos or playlists, scale appropriately within a content area. This can done by hand but it's difficult to maintain, especially with CMS's and multiple editors. Reframe.js solves this issue—perfectly!

Alternatively, noframe.js is provided. Noframe.js scales selected elements at a fixed ratio but does not manipulate the dom's element structure at all! This keeps things like analytic events that run on embedded content intact!

Installing

NPM

npm i reframe.js --save

Yarn

yarn add reframe.js

Setup

  1. Add dist/reframe.js
  2. reframe the element you'd like to re-frame.

Examples

reframe('iframe'); // Wrap all iFrames in the page
reframe(document.getElementById('my-frame')); // Pass a DOM element
reframe(document.querySelectorAll('.my-targets')) // Pass a live node list

Elements that have been wrapped with reframe will not be wrapped twice.

How?

Reframe.js wraps a specified element in a div that is an intrinsic ratio of the original element. This plugin is great for embedded content like iframes or videos.

Why Reframe.js?

Reframe.js is inspired by FitVids and does what FitVids does but without the need for jQuery. This makes the plugin highly valuable when including it in a module that has to be very small and with minimal dependencies. Here's a basic codepen example.

This plugin is small - ~1.3kb unminified and is meant to do 1 thing - wrap elements that aren't responsive and make them responsive. 💪

Options

If you'd like to not use the classname 'js-reframe', just use your own.

reframe('iframe', 'my-classname');

jQuery

Reframe.js works with jQuery or Zepto. As of version 2.0.0, use jquery.reframe.js for jQuery or Zepto.

$('iframe').reframe();

// While using a custom class name
$('iframe').reframe('my-classname');

🌐 Noframe.js

Noframe.js makes the same ratio as Reframe.js using css calc.

Noframe.js's doesn't wrap the element you'd like to be responsive. It, instead, does a calculation based on its or a parent element's max-width. Here's a basic codepen example.

Noframe.js Notes

  • The reframed element requires a parent element with a max width to scale above the selected elements intial size otherwise the reframed element will only scale below its initial size. 👍

Setup

  1. Add dist/noframe.js
  2. noframe the element you'd like to re-frame.

Examples

noframe('iframe');
noframe('iframe', 'parent');

jQuery

Noframe.js works with jQuery or Zepto. As of version 2.0.0, use jquery.noframe.js for jQuery or Zepto.

$('iframe').noframe();
$('iframe').noframe('parent');

Reframe.js or Noframe.js?

Reframe.js offers the simplest solution to making elements scale at an intrinsic ratio.

Noframe.js doesn't wrap the selected element to make it scale at an intrinsic ratio. Noframe.js is the ideal solution when various events, like tracking events, could be affected when an element is wrapped. It does require a width or max-width which can involve a bit more setup awareness.


Created and maintained by Jeff Wainwright with Dollar Shave Club Engineering.

reframe.js's People

Contributors

bfred-it avatar briangonzalez avatar deansimcox avatar greenkeeper[bot] avatar jakiestfu avatar koenpunt avatar mohandere avatar pwfisher avatar renovate[bot] avatar sudo-suhas avatar yowainwright avatar

Stargazers

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

Watchers

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

reframe.js's Issues

CSS

Is it possible to provide the styles as a .css file in addition to Sass format?

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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (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 🌴

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

Version 2.4.0 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.3.0
Type devDependency

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

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

Commits

The new version differs by 10 commits.

  • 44ca158 update utils changelog
  • a3728d7 bump eslint-module-utils to v2.1.0
  • 3e29169 bump v2.4.0
  • ea9c92c Merge pull request #737 from kevin940726/master
  • 8f9b403 fix typos, enforce type of array of strings in allow option
  • 95315e0 update CHANGELOG.md
  • 28e1623 eslint-module-utils: filePath in parserOptions (#840)
  • 2f690b4 update CI to build on Node 6+7 (#846)
  • 7d41745 write doc, add two more tests
  • dedfb11 add allow glob for rule no-unassigned-import, fix #671

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 conventional-changelog-cli is breaking the build 🚨

The devDependency conventional-changelog-cli was updated from 2.0.11 to 2.0.12.

🚨 View failing branch.

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

conventional-changelog-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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).

Commits

The new version differs by 40 commits.

  • 97ad96f Publish
  • 1041d81 chore: update handlebars dependency (#412)
  • d3c2432 chore(deps): lock file maintenance
  • b6439a7 chore(deps): lock file maintenance
  • f93f90d chore(deps): lock file maintenance
  • 3f18d2f chore(deps): lock file maintenance
  • 943542f chore(deps): lock file maintenance
  • d079df6 chore(deps): lock file maintenance
  • b97f113 chore(deps): lock file maintenance
  • 9fd3e81 chore(deps): lock file maintenance
  • e536fe9 chore(deps): lock file maintenance
  • e8d8b7a chore(deps): lock file maintenance
  • 4807f13 chore(deps): lock file maintenance
  • 5a4bf80 chore(deps): lock file maintenance
  • eb8ba01 chore(deps): lock file maintenance

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

Is calc() necessary in noframe.js?

This script is great! Love the idea of using inline styles to make an iframe responsive instead of wrapping it in a div.

I was just checking out the CodePen demo in Chrome and noticed the inline styles looked like this:

max-height: calc(315px);
height: calc(56.25vw);

It seems that Chrome is automatically simplifying the calc() formulas, e.g. calc(560px * 315/560) was converted to calc(315px).

Seems like it might make sense to do this calculation in the JS and omit calc() for simplicity’s sake but wanted to run it by you before submitting a PR.

Thanks!

Example?

Can you create a Codepen or Fiddle which demos this plugin?

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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (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 🌴

Script breaks when width and height attributes are not set

The issue

The reframe script breaks with the error Uncaught TypeError: Cannot read property 'indexOf' of null if no size attributes are found on the frame element.

Requested Update

Either implement a check to see if the frame has intrinsic size, and then use attributes as a fallback, or update documentation to clarify that these attributes are required.

As a workaround for now, I simply loop through the frames before and add the necessary attributes before I call reframe.

Why Is This Update Needed?

I'm using this script on a site that uses a cms (wordpress), and I can't assume every iframe/embed code will have the required size attributes.

Are There Examples Of This Requested Update Elsewhere?

This issue may be related to this pr #88

The issue can be easily replicated by simply removing the width and height attributes from the iframe in the codepen demo https://codepen.io/jakob-maudience/pen/oNNgzQd

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

The devDependency rollup was updated from 1.9.2 to 1.9.3.

🚨 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v1.9.3

2019-04-10

Bug Fixes

  • Simplify return expressions that are evaluated before the surrounding function is bound (#2803)

Pull Requests

  • #2803: Handle out-of-order binding of identifiers to improve tree-shaking (@lukastaegert)
Commits

The new version differs by 3 commits.

  • 516a06d 1.9.3
  • a5526ea Update changelog
  • c3d73ff Handle out-of-order binding of identifiers to improve tree-shaking (#2803)

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 🌴

Multiple selectors prevented from reframing

Requested Update

Remove this specific line of code from jquery.reframe.js, which breaks the reframing for-loop if an element has a percentage width:

if (wAttr.indexOf('%') > -1 || frame.style.width.indexOf('%') > -1) return;

Why Is This Update Needed?

I am working on a site which has multiple content Authors, and have come across an instance whereby multiple videos within iFrames were embedded on the page. The first had a percentage width, the others did not. As a result of the above line of code, the responsive wrapping container was not applied to the subsequent iFrames.

Because the first selector has a width attribute set as a percentage, it breaks out of the for-loop which wraps the elements in a responsive wrapper, and no further elements of the current selector get processed.

Since the element is reframed in a responsive container, I don't believe this line of code is necessary. Happy to be proven wrong however :)

Thanks

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

The devDependency rollup 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.

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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Commits

The new version differs by 6 commits.

  • 9af119d 1.19.0
  • b3f361c Update changelog
  • 456f4d2 Avoid variable from empty module name be empty (#3026)
  • 17eaa43 Use id of last module in chunk as name base for auto-generated chunks (#3025)
  • 871bfa0 Switch to a code-splitting build and update dependencies (#3020)
  • 2443783 Unified file emission api (#2999)

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 🌴

YouTube events and data api

  • embed two youtube videos
  • bind youtube events onstatechange
  • enable reframe on the videos

do the onstatechange events still fire reliably?
fitvids.js has this problem where youtube video onstatechange events no longer fire because the original player was removed from the DOM and then re-added (which it looks like reframe does too)

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

The devDependency gulp-uglify was updated from 3.0.1 to 3.0.2.

🚨 View failing branch.

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

gulp-uglify 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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).

Release Notes for v3.0.2

A relatively small maintenance release adjusting dependencies.

Features

  • Lodash is removed in favor of lighter dependencies specifically for the features used. intelli-espower-loader was also removed, as it's no longer compatible with the full suite of Node.js releases tested.
Commits

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

The devDependency rollup was updated from 1.27.6 to 1.27.7.

🚨 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v1.27.7

2019-12-01

Bug Fixes

  • Fix a scenario where a reassignments to computed properties were not tracked (#3267)

Pull Requests

Commits

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

The devDependency rollup was updated from 1.1.2 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.

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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).

Commits

The new version differs by 17 commits.

  • 60e8df2 1.2.0
  • 56ff3e3 Update changelog
  • 19a7727 Reimplement variable deconflicting logic (#2689)
  • fe84e00 Update changelog
  • db42a04 Prevent final resolution and facade creation for inlined dynamic imports (#2677)
  • 4d082b0 Respect rendered exports when generating chunk hashes (#2695)
  • 14a17af Correctly render function expression inside simplified expression statements. (#2696)
  • 0a46310 Add a fix for MaxListenersExceededWarning (#2700)
  • 1454b90 Update rollup-pluginutils (#2703)
  • d883243 Update changelog
  • f8faa4b Allow config files to contain non-default exports (#2673)
  • d6a865e Update changelog
  • 1ae20fc Improve type of RollupOutput.output (#2679)
  • 7f79ab1 Update changelog
  • c702f3a Fix typo in export-globals test (#2693)

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 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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (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 babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/core was updated from 7.2.0 to 7.2.2.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a 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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (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 🌴

Pull tests out of src

Tests do not belong in the src directory. They are not the source code for your project, rather, they are auxiliary scripts meant to support the src.

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:

  • Replaced the old Node.js version in your .nvmrc with the new one

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 🌴

Uncaught TypeError: e.reframe is not a function

Hi

There is an issue with $ shorthand function.

window.$ is undefined in my case, instead window.jQuery works for me.

To fix this issue i did changed plugin code from,

if (window.$) {
     window.$.fn.extend({
       reframe: function reframeFunc(cName) {
         return reframe(this, cName);
      }
  });
}

To

if (window.jQuery) {
     window.jQuery.fn.extend({
       reframe: function reframeFunc(cName) {
         return reframe(this, cName);
      }
  });
}

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

The devDependency qunit was updated from 2.9.1 to 2.9.2.

🚨 View failing branch.

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

qunit 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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ci/circleci: lint: Your tests failed on CircleCI (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).

Release Notes for 2.9.2
  • Core: Ensuring semaphores are balanced when timeout occurs (#1376)
  • Docs: Fix the casing for autostart and noglobals (#1373)
  • HTML Reporter: Avoid inline styles to support CSP without 'unsafe-inline'
  • Buid: Update 'resolve' to v1.9.0
Commits

The new version differs by 7 commits ahead by 7, behind by 1.

  • 0f727f1 2.9.2
  • 9e5e590 Build: Prepare 2.9.2 release, including authors and history update
  • ba7453a Core: Ensuring semaphores are balanced when timeout occurs (#1376)
  • 766db37 Docs: Fix the casing for autostart and noglobals (#1373)
  • 620ef5c HTML Reporter: Avoid inline styles to support CSP without 'unsafe-inline'
  • 1bea540 Buid: Update 'resolve' to v1.9.0
  • 1a30398 Build: Updating the master version to 2.9.2-pre.

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.14.2 to 1.14.3.

🚨 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v1.14.3

2019-06-06

Bug Fixes

  • Generate correct external imports when importing from a directory that would be above the root of the current working directory (#2902)

Pull Requests

Commits

The new version differs by 4 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 conventional-changelog-cli is breaking the build 🚨

The devDependency conventional-changelog-cli was updated from 2.0.5 to 2.0.7.

🚨 View failing branch.

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

conventional-changelog-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
  • ci/circleci: build: Your tests failed on CircleCI (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.