<StarRatingInput interactive={false} />

Say User A inputs a rating of 3 stars using this input. It would be nice to be able to display 3 stars as User A's rating to User B, and not allow User B to change the stars shown on hover.

| 🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️ | | --- | | This version of Greenkeper will be shutdown on May 31st. | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Hello lovely humans,

mocha just published its new version 3.4.0.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As mocha 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 :muscle:

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 170 commits .

• 7554b31 Add Changelog for v3.4.0
• 9f7f7ed Add --trace-warnings flag
• 92561c8 Add --no-warnings flag
• ceee976 lint test/integration/fixtures/simple-reporter.js
• dcfc094 Revert "use semistandard directly"
• 93392dd no special case for macOS running Karma locally
• 4d1d91d --allow-uncaught cli option
• fb1e083 fix allowUncaught in browser
• 4ed3fc5 Add license report and scan status
• fb1687e :ship: Release v3.3.0
• 1943e02 Add Changelog for v3.3.0
• 861e968 Refactor literal play-icon hex code to a var
• 1d3c5bc Fix typo in karma.conf.js
• 9bd9389 Fix spec paths in test HTML files
• 0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)

There are 170 commits in total. See the full diff.

Hello lovely humans,

browserify just published its new version 14.3.0.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As browserify 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 :muscle:

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 12 commits .

• cd01926 14.3.0
• 08caf04 changelog
• ad5060d Merge pull request #1710 from substack/https-browserify-1
• 7c7b4d4 update https-browserify to ^1.0.0
• 18e1d65 14.2.0
• 0e1a7a0 add cli support for --transform-key to support mode's like production/staging/etc..
• a5aa660 Merge pull request #1701 from wogsland/doc-fix
• ae281bc Fixed documentation formatting that was bugging me
• fe8c57b async test for node 7
• 06a47d1 14.1.0
• 67ea8b1 Merge branch 'patch-1' of https://github.com/natevw/node-browserify
• ea6c299 Write to temp outfile until success, fixes #899

See the full diff.

| ✨ Try the all new Greenkeeper GitHub Integration ✨ | | --- | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Screencast

https://ikr.su/h/react-star-rating-input/demo.html [Error] ReferenceError: Can't find variable: Intl (anonymous function) (bundle.js, line 1) s (bundle.js, line 1) (anonymous function) (bundle.js, line 1) (anonymous function) (bundle.js, line 1) s (bundle.js, line 1) (anonymous function) (bundle.js, line 1) (anonymous function) (bundle.js, line 1) (anonymous function) (bundle.js, line 1) s (bundle.js, line 1) (anonymous function) (bundle.js, line 1) (anonymous function) (bundle.js, line 1) (anonymous function) (bundle.js, line 1) (anonymous function) (bundle.js, line 1) s (bundle.js, line 1) e (bundle.js, line 1) global code (bundle.js, line 1)

| 🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️ | | --- | | This version of Greenkeper will be shutdown on May 31st. | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Hello lovely humans,

jsdom just published its new version 11.0.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of jsdom. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 55 commits .

• 0f4128d Version 11.0.0
• be65539 Fix event handler property generation to properly rely on runScripts
• 38c430f Factor out runScripts option tests
• ecf7449 Do not submit disconnected form elements
• 5f3cbd6 Properly implement event handler properties/attributes
• 3eb19e7 Remove a few more now-redundant toString()s
• b1b7f23 Refactor XHR's send() implementation
• 7d950c4 Delete keygen from default stylesheet
• 5151546 Remove other unsupported CSS features from the default stylesheet
• dfc9430 Delete webkit prefixes and other internal selectors in default CSS
• 56fbd0d Support ArrayBufferViews in xhr.send()
• ce13678 Disable yet another flaky-on-CI XHR test
• dabf1a4 Remove createCDATASection from benchmarks
• 2d257ef Update benchmark runner to support the new API
• 1833f78 Use Set instead of Array for HTMLCollection keys

There are 55 commits in total. See the full diff.

| 🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️ | | --- | | This version of Greenkeper will be shutdown on May 31st. | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Hello lovely humans,

uglify-js just published its new version 3.0.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of uglify-js. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

GitHub Release

The new version differs by 129 commits .

• 7313465 v3.0.0
• 2c7ee95 fix unsafe on evaluate of reduce_vars (#1870)
• ecf3563 kill opera (#1869)
• dee5a27 enhance collapse_vars (#1862)
• 5a25d24 rename variables for better readability (#1863)
• bffdc8d update test/benchmark.js resources (#1864)
• 69b5663 restore report of supported options (#1861)
• ea92897 improve literal return optimization (#1860)
• 2cb55b2 enforce toplevel on other compress options (#1855)
• bbb5f2a Update ISSUE_TEMPLATE.md (#1846)
• 76d19b6 fix fuzzer on this (#1842)
• 9e62628 fix unused on for-in statements (#1843)
• 9bf72cf improve parser under "use strict" (#1836)
• 64d7443 update README for 3.x (#1840)
• 45ce369 fix AST_For.init patch-up in drop_unused() (#1839)

There are 129 commits in total. See the full diff.

Hello lovely humans,

jsdom just published its new version 10.0.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of jsdom. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 67 commits .

• 50ebb59 Version 10.0.0
• c854f7e Small updates to the readme and to JS feature usage
• 380e2fe Forward approved preflight headers to request during XHR
• 3a1c2e0 Fix htmlElement.dir and implement document.dir
• 3aca01a Update / API to match current specs
• fa74ef9 Fix origin-checking logic in postMessage
• 4513ba1 Improve xhr.open not enough args error message
• 461c638 Handle setting innerHTML to the empty string
• 58a7028 Overhaul the public jsdom API
• e068779 Version 9.12.0
• 580e557 Fix clearTimeout in web workers
• 8838684 Fix event.stopImmediatePropagation()
• 5069d64 Update Option constructor and text/value for spec compliance
• 7f148e8 Preserve URL fragments across redirects in jsdom.env
• 0454f04 Enable support for the canvas-prebuilt package

There are 67 commits in total. See the full diff.

| ✨ Try the all new Greenkeeper GitHub Integration ✨ | | --- | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Screencast

Hello lovely humans,

uglify-js just published its new version 2.8.14.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

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 :muscle:

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

GitHub Release

The new version differs by 235 commits .

• 30a7504 v2.8.14
• a3cc3a9 make expect_stdout work on Node.js 0.12 (#1623)
• 96f8bef fix commit 88fb83a (#1622)
• cd58635 fix AST_Binary.lift_sequences() (#1621)
• 274331d transform String.charAt() to index access (#1620)
• 0489d6d handle runtime errors in expect_stdout (#1618)
• fb09283 fix top-level directives in compress tests (#1615)
• b7c112e Add --in-source-map inline documentation (#1611)
• b2b8a0d v2.8.13
• ac40301 fix chained evaluation (#1610)
• 3563d8c extend test/run-tests.js to optionally execute uglified output (#1604)
• 5ae04b3 make collapse_vars consistent with toplevel (#1608)
• a80b228 fix hoist_vars on reduce_vars (#1607)
• cf4bf4c fix stack issues with AST_Node.evaluate() (#1603)
• 8223b2e fix AST_Node.optimize() (#1602)

There are 235 commits in total. See the full diff.

| ✨ Try the all new Greenkeeper GitHub Integration ✨ | | --- | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Screencast

Hello lovely humans,

sinon just published its new version 2.0.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of sinon. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 623 commits (ahead by 623, behind by 25).

• 15a0038 Add dist file to docs
• 108ac04 Update docs/changelog.md and set new release id in docs/_config.yml
• 3f5c869 Add release documentation for v2.0.0
• 02a6ff6 2.0.0
• 224ec4f Update Changelog.txt and AUTHORS for new release
• c748bc5 Merge pull request #1325 from lucasfcosta/callsFake-docs
• fee959d Merge pull request #1297 from lucasfcosta/getters-setters-new-api
• 1bda7c4 Merge pull request #1326 from lucasfcosta/remove-unused-chain-behavior
• 70e96f5 Remove unused chain behavior
• bdd3f82 Add docs for the new callsFake behavior
• ad58467 Add docs for the new API get and set behaviors
• eb7f90f Add names to previously anonymous getter and setter test functions
• e852f4f Add restore method for stubbed property descriptors
• 5bbfa51 Allow stubbing getters and setters for function properties
• 278c2ce Add getters/setters stub behaviors

There are 250 commits in total. See the full diff.

| ✨ Try the all new Greenkeeper GitHub Integration ✨ | | --- | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Screencast

Hello lovely humans,

browserify just published its new version 14.0.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of browserify. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 20 commits .

• 691239d 14.0.0
• 60cd894 changelog: 14.0.0
• d7ea3dd Merge pull request #1678 from substack/buffer-5
• 4f5d93b test: pass Uint8Array into vm context for buffer v5
• ae33350 Update 'buffer' to v5.x
• 6efcd65 13.3.0
• cbc20ac use carat on assert package
• 30b30ca Merge branch 'patch-2' of https://github.com/jscissr/node-browserify
• 1635157 13.2.0
• d2392a4 Merge branch 'master' of https://github.com/laurynasl-wix/node-browserify
• bf061d8 Allow configuring transformKey option for module-deps
• 9e3b11e Merge branch 'master' of https://github.com/Abhinay077/node-browserify
• c3a4424 13.1.1
• 10b93d8 use cached-path-relative fixes from https://github.com/substack/node-browserify/pull/1544
• 71240c2 Update package.json

There are 20 commits in total. See the full diff.

| ✨ Try the all new Greenkeeper GitHub Integration ✨ | | --- | | With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Screencast

Hello lovely humans,

insert-css just published its new version 2.0.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of insert-css. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

The new version differs by 14 commits .

• d13317d 2.0.0
• c0d2698 feat(usage): check usage and throw
• decc1cf Merge pull request #28 from classmarkets/master
• 2ee8670 Prevent usage without any css
• fad9931 Add test for function call with arguments
• a8eb15a Merge pull request #27 from substack/revert-26-master
• dd8dc5a Revert "Fix cannot read property of undefined"
• d5aea2b Merge pull request #26 from classmarkets/master
• 7ae9b41 Fix cannot read property of undefined
• e133b27 v1.1.0
• 54a0a0b Merge pull request #25 from jonaskello/named_export
• edfd426 Add named export
• 68f4d10 Merge pull request #23 from mk-pmb/strip-bom
• dbd8882 Strip potential UTF-8 BOM if CSS was read from a file.

See the full diff.

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? :zap: greenkeeper upgrade}