Git Product home page Git Product logo

jonathanweiss / component-manager Goto Github PK

View Code? Open in Web Editor NEW
7.0 7.0 0.0 290 KB

Micro utility (583 bytes compressed) that manages initialising and teardown of components (e.g. jQuery plugins) as soon as specific DOM nodes are added into the document, respectively removed from it.

License: MIT License

JavaScript 63.20% HTML 36.80%
components manager microlib mutationobserver utility-library vanilla-javascript vanilla-js

component-manager's Introduction

Hi there 👋

Metrics

component-manager's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar jonathanweiss avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

component-manager's Issues

An in-range update of karma-coverage is breaking the build 🚨

Version 1.1.2 of karma-coverage was just published.

Branch Build failing 🚨
Dependency karma-coverage
Current Version 1.1.1
Type devDependency

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.1.2

Bug Fixes

  • build: Update to lodash 4 (d6d21d2), closes #242
  • reporter: replace colons in the output path (3b2bffa)

BREAKING CHANGES

  • reporter: the output folder names change, they no longer contain :
Commits

The new version differs by 12 commits.

  • 070bba3 chore: release v1.1.2
  • 9319dfb chore: update contributors
  • 9433b24 Merge pull request #339 from johnjbarton/fix-242
  • bf599db Merge pull request #344 from AndrewLane/AndrewLane-patch-1
  • 595ab98 Fix exclude typo on the check object
  • d6d21d2 fix(build): Update to lodash 4
  • 954a555 Merge pull request #345 from johnjbarton/engines
  • d4695cf Update travis to match parent karma project
  • 54737bf chore: add grunt-cli npm test works out of the box
  • 2bc4aa5 docs: add json-summary report type
  • 3b2bffa fix(reporter): replace colons in the output path
  • 1a876d5 docs: Added none as possible value for type

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 karma-chrome-launcher is breaking the build 🚨

Version 2.1.0 of karma-chrome-launcher just got published.

Branch Build failing 🚨
Dependency karma-chrome-launcher
Current Version 2.0.0
Type devDependency

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

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

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

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/jonathanweiss/component-manager/builds/228037929?utm_source=github_status&utm_medium=notification)

Release Notes v2.1.0

Features

  • add support for custom user-data-dir in Chromium (579fcfc), closes #89
  • add support for headless Chrome/ChromeCanary (7446181)
Commits

The new version differs by 19 commits0.

  • 2267df1 chore: release v2.1.0
  • f993c48 chore: update contributors
  • 7446181 feat: add support for headless Chrome/ChromeCanary
  • d81da0e Merge pull request #116 from maieutiquer/patch-1
  • 37513a9 clean-up irrelevant comment
  • a0235a2 Merge pull request #115 from karma-runner/greenkeeper-standard-10.0.0
  • 8987630 chore(package): update standard to version 10.0.0
  • 1e4b4ff Merge pull request #110 from karma-runner/greenkeeper-standard-9.0.2
  • 5d559e7 chore(package): update standard to version 9.0.2
  • fbe91ca Merge pull request #92 from karma-runner/greenkeeper-grunt-auto-release-0.0.7
  • 4a7efc0 chore(package): update grunt-auto-release to version 0.0.7
  • 7abf72d Merge pull request #109 from karma-runner/greenkeeper-sinon-2.0.0
  • e4d38c0 chore(package): update sinon to version 2.0.0
  • b9f9214 Merge pull request #84 from karma-runner/greenkeeper-mocha-3.2.0
  • f5c5874 Merge branch 'master' into greenkeeper-mocha-3.2.0

There are 19 commits in total.

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

Version 3.0.6 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.5
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.6

 

Commits

The new version differs by 6 commits0.

  • 050474a v3.0.6
  • f6c805a print package name alongside version in CLI (#1946)
  • 9464d3c fix parsing of property access after new line (#1944)
  • f18abd1 minor fixes to README.md
  • 3be06ad reorg README for 3.x (#1942)
  • 265008c improve keyword-related parser errors (#1941)

false

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 karma-firefox-launcher is breaking the build 🚨

The devDependency karma-firefox-launcher was updated from 1.1.0 to 1.2.0.

🚨 View failing branch.

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

karma-firefox-launcher 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 13 commits.

  • a398dae chore(release): 1.2.0
  • c1a3939 fix: Detect and kill browser process when launcher process is being used (#103)
  • c3fea39 chore: Update dependencies
  • 2e94873 chore: Add missing is-wsl entry to yarn.lock
  • b4e260e feat: Add support for running Windows Firefox from WSL
  • 2443631 chore: Add self to contributors
  • 2dca609 chore: Update dev dependencies
  • 16e6673 chore: Sort contributors list [skip ci]
  • 9e86d04 chore: Drop support for Node 6 (#98)
  • 540c1dd fix: Add -wait-for-browser
  • 6377ee3 fix: Look for other paths for Firefox Nightly on Windows and Mac
  • b9455c8 chore: Fix travis (#97)
  • 0e37f76 feat(headless): add enable remote debugging by default

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 karma-chrome-launcher is breaking the build 🚨

Version 2.2.0 of karma-chrome-launcher just got published.

Branch Build failing 🚨
Dependency karma-chrome-launcher
Current Version 2.1.1
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v2.2.0

Features

Commits

The new version differs by 6 commits.

  • b01cea1 chore: release v2.2.0
  • 40e96e2 chore: update contributors
  • 998824d Merge pull request #135 from ishitatsuyuki/chromium-headless
  • 7a12021 feat: add ChromiumHeadless
  • 96d84aa Merge pull request #126 from mgol/patch-1
  • 2a02494 refactor: remove incorrect comment

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

Version 5.2.3 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 5.2.2
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 5.2.3

Patches

  • Corrected signal handling inside Docker containers: 604f335
  • Bumped dependencies to the latest version: 2a319c8
Commits

The new version differs by 8 commits.

  • 132f662 5.2.3
  • 2a319c8 Bumped dependencies to the latest version
  • 604f335 Corrected signal handling inside Docker containers
  • 25fa53c fix(package): update clipboardy to version 1.1.4 (#228)
  • 2063fc7 chore(package): update lint-staged to version 4.0.0 (#226)
  • d44783f fix(package): update opn to version 5.1.0 (#221)
  • 7d56369 chore(package): update lint-staged to version 3.6.1 (#220)
  • 089310e chore(package): update prettier to version 1.4.4 (#219)

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

Version 3.0.4 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.3
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.4

 

Commits

The new version differs by 5 commits0.

false

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

Version 3.0.21 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.20
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.21

 

Commits

The new version differs by 3 commits.

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

Version 5.1.3 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 5.1.2
Type devDependency

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

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

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


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 5.1.3

Patches

  • Fix(package): update clipboardy to version 1.1.0: #156
  • Chore(package): update eslint-config-prettier to version 1.6.0: #158
  • Invalidate cache of Slack badge: 0b9fde0
Commits

The new version differs by 4 commits .

  • b987a17 5.1.3
  • 0b9fde0 Invalidate cache of Slack badge
  • ac84b47 chore(package): update eslint-config-prettier to version 1.6.0 (#158)
  • 1517d41 fix(package): update clipboardy to version 1.1.0 (#156)

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

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

More information on this issue

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

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

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


FAQ and help

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


Your Greenkeeper Bot 🌴

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

Version 3.0.5 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.4
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.5

 

Commits

The new version differs by 9 commits0.

  • ff526be v3.0.5
  • e005099 fix & improve coverage of estree (#1935)
  • 504a436 Tweak README Notes (#1934)
  • 3ca9022 fix bugs with getter/setter (#1926)
  • fd09512 document 3 max passes (#1928)
  • 9e29b6d clarify wording (#1931)
  • c391576 remove support for const (#1910)
  • ac73c5d avoid arguments and eval in reduce_vars (#1924)
  • 547f41b add documentation for side_effects & [#@]__PURE__ (#1925)

false

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 🌴

Examine failing test in IE11

  ComponentManager
    ✓ attaches itself to the Window object when RequireJS is not available
    ✓ registers each component only once
    ✓ executes the "onAdd" callback when a DOM node with the designated name is added to the document
    ✗ executes the "onRemove" callback when a DOM node with the designated name is removed from the document
    Expected spy onRemove to have been called.
       at Anonymous function (test/manager.spec.js:73:7)

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

Version 3.0.9 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.8
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.9

 

Commits

The new version differs by 2 commits.

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

Version 3.0.3 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.1
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.3

 

Commits

The new version differs by 11 commits0.

  • aae7d49 v3.0.3
  • 0459af2 Update issue template: change harmony to uglify-es (#1900)
  • 04f2344 Remove unnecessary git clone instructions in README (#1897)
  • bad9d5c Change harmony to uglify-es in master README (#1895)
  • a0f5f86 gracefully handle non-Error being thrown (#1893)
  • 41996be extend test timeout
  • 5fd8244 v3.0.2
  • c14e280 print error stack in CLI (#1890)
  • bc3fa78 mention minify().error
  • 8c7c107 update minify() usage in test/ufuzz.js (#1888)
  • 3dd328d [3.x] fix documentation for beautify options (#1882)

false

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

Version 3.3.0 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 3.2.10
Type devDependency

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

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

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


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 3.3.0

Minor Changes

  • Add title attributes to file links: #106

Patches

  • Remove the bullet characters: #104
  • Remove unused code: #107
  • Fix(package): update fs-promise to version 2.0.0: #108
  • Copy local URL to clipboard: 62cb176

Credits

Huge thanks to @disquisition and @thorn0 for their help!

Commits

The new version differs by 6 commits .

  • 0d11a17 3.3.0
  • 62cb176 Copy local URL to clipboard
  • 890d3c2 fix(package): update fs-promise to version 2.0.0 (#108)
  • f0fc9d4 Remove unused code (#107)
  • 5eb39ef Add title attributes to file links (#106)
  • 95c3d89 Remove the bullet characters (#104)

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

Version 10.0.3 of standard just got published.

Branch Build failing 🚨
Dependency standard
Current Version 10.0.2
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v10.0.3
  • Internal changes (incremented dependency versions)
Commits

The new version differs by 99 commits.

  • 91e80a1 10.0.3
  • 82a0d5c changelog
  • d22676e Merge pull request #963 from daper/patch-1
  • cfb84fe Remove tilde to lock down eslint-config-standard-jsx version
  • 4a6e0d0 Update dependecy of eslint-config-standard-jsx
  • ac9e09e Merge pull request #961 from igorsantos07/patch-1
  • 873bc9b Adding valid example for no-unsafe-negation
  • f00b169 more feross/standard -> standard/standard
  • 9770303 Merge pull request #954 from standard/security
  • 8cc2285 Add a security policy
  • 2fa8b0f change more feross/standard -> standard/standard
  • e79a692 Merge branch 'devjin0617-translation-kr'
  • 34490f7 Merge branch 'translation-kr' of https://github.com/devjin0617/standard into devjin0617-translation-kr
  • 6d59566 Merge pull request #953 from standard/translations
  • 3895bc6 move english readme/rules to docs/ folder

There are 99 commits in total.

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

Version 3.0.25 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.24
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.25

 

Commits

The new version differs by 11 commits.

  • 4e12a6f v3.0.25
  • b35dfc2 reject malformed CLI parameters (#2239)
  • 9e1da92 ensure ie8 works with mangled properties (#2238)
  • a5ffe2c drop unused builtin globals under unsafe (#2236)
  • 9282e7b fix unsafe evaluate of Object static methods (#2232)
  • 5229cb2 drop unused compound assignments (#2230)
  • 458e3e1 enhance passes (#2229)
  • c615a1e fix gzip stream in test/benchmark.js (#2228)
  • 10a938c enhance source mapping on IIFEs (#2224)
  • 4956ad3 benchmark gzipped output (#2220)
  • 145874e docs: update benchmarks using node 8, add babili (#2218)

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

Version 3.0.10 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.9
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.10

 

Commits

The new version differs by 6 commits.

  • d3c4a8e v3.0.10
  • 7e164ab add "es5" to package.json keywords (#1980)
  • 22aedef document minify() option toplevel (#1979)
  • 58fae7d enhance if_return to handle return void... (#1977)
  • 5bf8d7e document 3.x minify() does not throw errors (#1975)
  • 1df9d06 document minify warnings and add an error example (#1973)

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

Version 3.0.7 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.6
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.7

 

Commits

The new version differs by 2 commits.

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 karma-sauce-launcher is breaking the build 🚨

Version 1.2.0 of karma-sauce-launcher just got published.

Branch Build failing 🚨
Dependency karma-sauce-launcher
Current Version 1.1.0
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.2.0

Features

  • config: add proxy option (bae758a)
  • config: allow SE traffic to be sent via Sauce Connect's Relay (0ac67d4)
  • config: pass parentTunnel to selenium (bae326f)
  • deps: upgrade sauce connect (e792677)
  • launcher: expose commandTimeout, idleTimeout, maxDuration options (3fe1c75), closes #62
Commits

The new version differs by 13 commits.

  • 004d61d chore: release v1.2.0
  • f783f63 chore: update contributors
  • a21fbd9 chore(deps): update dev dependencies
  • 79c70c2 feat(config): expose commandTimeout, idleTimeout, maxDuration options
  • f607303 Merge branch 'master' of https://github.com/JamieMason/karma-sauce-launcher into JamieMason-master
  • 0362ad5 docs(readme): fix SauceLabs doc links
  • 0ac67d4 feat(config): allow SE traffic to be sent via Sauce Connect's Relay
  • 0219065 docs(readme): add hint to platform configurator
  • bae326f feat(config): pass parentTunnel to selenium
  • bae758a feat(config): add proxy option
  • e792677 feat(deps): upgrade sauce connect
  • 79b688c chore(travis): update build config
  • 3fe1c75 feat(launcher): expose commandTimeout, idleTimeout, maxDuration options

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

Version 2.7.0 of jasmine-core just got published.

Branch Build failing 🚨
Dependency jasmine-core
Current Version 2.6.4
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 2.7.0

Please see the release notes.

Commits

The new version differs by 40 commits ahead by 40, behind by 6.

  • b256741 bump version to 2.7.0
  • 1d4a2b5 Merge branch 'user-context' of https://github.com/darthjee/jasmine into darthjee-user-context
  • b0aac6b Add class UserContext
  • 543e056 Merge branch 'jberney-master'
  • 7dfc5f5 Send unfocused tests through the same queue as focused tests
  • 4cce726 Update github issue and PR templates
  • 3116410 Get the casing right for IE8
  • f71218a Allow IE8 to be weird when pretty printing
  • 22e9d6d PrettyPrinter allows an object to have a toString that isn't a function
  • aa72b0b Simplified rounding code in toBeCloseTo
  • 9f3952f Merge branch 'vanduynslagerp-fix-tobecloseto'
  • c604012 Fix rounding in toBeCloseTo
  • 6aa069d IE 8&9 use setTimeout to clearStack so mock clock gets tricky
  • 585287b When stop on failure is enabled, skip subsequent it() and beforeEach().
  • de862f8 Only clear out the spec param for Run all link

There are 40 commits in total.

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

Version 3.0.22 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.21
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.22

 

Commits

The new version differs by 2 commits.

  • 7659ea1 v3.0.22
  • bdeadff improve usability of name cache under minify() (#2176)

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

Version 2.6.2 of jasmine-core just got published.

Branch Build failing 🚨
Dependency jasmine-core
Current Version 2.6.1
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 2.6.2

Please see the release notes

Commits

The new version differs by 7 commits.

  • 5d1d19f Bump version to 2.6.2
  • 4f49288 Built distribution
  • b9adc76 Clear the stack if onmessage is called before the previous invocation finishes
  • 5ac3e21 Merge branch 'interleaved-suites' of https://github.com/sgravrock/jasmine into sgravrock-interleaved-suites
  • b1e97cf Correctly route errors that occur while a QueueRunner is clearing stack
  • 8e5823c Merge branch 'sgravrock-global-errors-rethrow'
  • 10f1220 Don't mask errors that occur when no handlers are installed

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

Version 3.0.23 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.22
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.23

 

Commits

The new version differs by 3 commits.

  • 2dde416 v3.0.23
  • 8b69a3d drop argument value after collapse_vars (#2190)
  • d40950b improve inline efficiency (#2188)

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 karma-jasmine-matchers is breaking the build 🚨

Version 3.8.3 of karma-jasmine-matchers was just published.

Branch Build failing 🚨
Dependency karma-jasmine-matchers
Current Version 3.7.0
Type devDependency

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

karma-jasmine-matchers 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

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

Version 6.0.2 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 6.0.1
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 6.0.2

Patches

  • Disable cache when --cache flag is set to 0: #245
  • Lockfile added: 4f7ef6f

Credits

Huge thanks to @fabe for his help!

Commits

The new version differs by 5 commits.

  • f4098ee 6.0.2
  • 4f7ef6f Lockfile added
  • 6d60755 Disable cache when --cache flag is set to 0 (#245)
  • d90f267 chore(package): update lint-staged to version 4.0.1 (#244)
  • 0faccbd chore(package): update husky to version 0.14.3 (#243)

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

Version 3.2.10 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 3.2.9
Type devDependency

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

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

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


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 3.2.10

Patches

  • Mention all old names: 4714bc8
  • Make command history available: 4081884
  • Only copy to clipboard for TTY: a650cf7
Commits

The new version differs by 4 commits .

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

Version 3.0.19 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.18
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.19

 

Commits

The new version differs by 2 commits.

  • f67a6b0 v3.0.19
  • 343ea32 ensure mangling works if catch reuses a scope variable (#2123)

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

Version 6.0.3 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 6.0.2
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 6.0.3

Patches

  • Fixed missing zero in one day cache number: #255

Credits

Huge thanks to @albertstill for his help!

Commits

The new version differs by 8 commits.

  • 667e605 6.0.3
  • c0e62a5 Bumped dependencies to the latest version
  • 8edb2c6 Fixed missing zero in one day cache number (#255)
  • dad260a fix(package): update args to version 3.0.4 (#254)
  • dbd254c chore(package): update prettier to version 1.5.3 (#251)
  • f746f56 fix(package): update fs-extra to version 4.0.0 (#250)
  • ee28226 fix(package): update boxen to version 1.2.0 (#249)
  • 6d769d6 fix(package): update path-type to version 3.0.0 (#246)

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

Version 3.0.8 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.7
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.8

 

Commits

The new version differs by 7 commits.

  • 43add94 v3.0.8
  • efcf167 make expect_stdout node version specific (#1963)
  • 6ed9091 fix docs for side_effects flag to reflect current behavior (#1966)
  • 569c21e improve RegExp handling (#1959)
  • 87c3a2c remove space_colon (#1960)
  • baef8bf update output options in readme (#1958)
  • 0813c53 remove Travis CI badge

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

Version 3.0.1 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 3.0.0
Type devDependency

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

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

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


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 3.0.1

Patches

  • Correct config props for async-to-gen: 20fe997
Commits

The new version differs by 2 commits .

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

Version 2.8.6 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 2.8.5
Type devDependency

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

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

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


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 12 commits .

  • 33b5f31 v2.8.6
  • 35a849d collapse assignment with adjacent subsequent usage (#1553)
  • b70591b handle variable declaration within catch blocks (#1546)
  • b33e7f8 improve unsafe on undefined (#1548)
  • 1f0333e stay safe with constants in IE8- (#1547)
  • eb98a7f fix handling of shebang and preamble (#1545)
  • 78d1bb9 fix a corner case in #1530 (#1552)
  • ea9ab9f resolve issue with outdated version of async (#1549)
  • ce54c9c disallow collapse_vars constant replacement in for-in statements (#1543)
  • 07accd2 process code with implicit return statement (#1522)
  • 18059cc compress numerical expressions (#1513)
  • b5e0e8c facilitate fix for #1531 (#1542)

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

Version 6.0.1 of serve just got published.

Branch Build failing 🚨
Dependency serve
Current Version 6.0.0
Type devDependency

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

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

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

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 6.0.1

Patches

  • Updated description to reflect current state: 54278bc
  • Prettified everything: 4c3c733 and 2e53727
  • Convert PORT environment variable to integer: #242
  • Better default caching for single page applications: 6655ed6
  • Improved syntax for determining port: dae446e
  • Fixed custom 404 pages: #218
  • Shorter error message for missing authentication flags: c16c721

Credits

Huge thanks to @danielking, @ro-savage and @rosszurowski for their help!

Commits

The new version differs by 15 commits.

  • 267bbb3 6.0.1
  • c16c721 Shorter error message for missing authentication flags
  • 0234ba4 Fixed custom 404 pages (#218)
  • dae446e Improved syntax for determining port
  • 6655ed6 Better default caching for single page applications
  • 2e53727 Prettified remaining code
  • 0c4e536 Convert PORT environment variable to integer (#242)
  • 4c3c733 Prettified everything
  • bac0fd9 Bumped dependencies to the latest version
  • 79a0b5d chore(package): update husky to version 0.14.2 (#241)
  • 4668cd6 fix(package): update chalk to version 2.0.0 (#238)
  • 1ed2159 chore(package): update prettier to version 1.5.2 (#236)
  • 0cf2f01 chore(package): update prettier to version 1.5.1 (#235)
  • f333a83 chore(package): update prettier to version 1.5.0 (#234)
  • 54278bc Updated description to reflect current state

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 🌴

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.