no23reason / react-geolocated Goto Github PK
View Code? Open in Web Editor NEWReact hook for using Geolocation API
Home Page: https://no23reason.github.io/react-geolocated/
License: MIT License
React hook for using Geolocation API
Home Page: https://no23reason.github.io/react-geolocated/
License: MIT License
After adding the declarations for TypeScript, it would help maintainability to add some test that would ensure those declarations are always up-to-date.
Use semantic-release to manage releases
In the current version of the TypeScript typings you can specify the injected props on the resulting component, i.e. you can write something like:
interface IDemoProps {
label: string;
}
class Demo extends React.Component<IDemoProps & GeolocatedProps, {}> {
render(): JSX.Element {
// implementation
}
}
const Wrapped = geolocated()(Demo);
<Wrapped
label="Hello"
isGeolocationAvailable={false} // this should not be possible
/>
I'd like to propagate the location fix to parent elements, but I can't seem to get it right. Would it be possible to adapt the demo to make that function more clear?
Branch | Build failing ๐จ |
---|---|
Dependency | react-dom |
Current Version | 15.6.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react-dom 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | @types/react |
Current Version | 16.4.13 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/react 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.
There is a collection of frequently asked questions. If those donโt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | eslint-plugin-react |
Current Version | 7.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-react 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 ๐ช
default-props-match-prop-types
rule (#1022 @webOS101)no-redundant-should-component-update
rule (#985 @jomasti)jsx-closing-tag-location
rule (#1206 @rsolomon)jsx-max-props-per-line
(#949 @snowypowers)nextProps
/prevProps
in no-unused-prop-types
(#1213 @jseminck)prop-types
(#1236 @gpeal)children
option to jsx-curly-spacing
(#857 @fatfisz)prefer-stateless-function
ignorePureComponents
option when using class expressions (#1122 @dreid)void-dom-elements-no-children
crash (#1195 @oliviertassinari)require-default-props
quoted defaultProps
detection (#1201)jsx-sort-props
bug with ignoreCase
and callbacksLast
options set to true
(#1175 @jseminck)no-unused-proptype
false positive (#1183 #1135 @jseminck)jsx-no-target-blank
to not issue errors for non-external URLs (#1216 @gfx)prop-types
quoted Flow types detection (#1132 @ethanjgoldberg)no-array-index-key
crash with key
without value (#1242 @jseminck)The new version differs by 105 commits.
cdfa56f
Update CHANGELOG and bump version
8bdb6a4
Update dependencies
5be0be3
Remove re-added require-extension rule documentation
e7836b5
Add ESLint 4.0.0 to peerDependencies
7cc380a
Fix indent errors
32bcb48
Merge pull request #1177 from fatfisz/curly-spacing-for-children
d57c115
Update the docs
6903f18
Add back the support for the previous config
5515130
Add more mixed tests
408e1b1
Add the "children" property of the config
65135b8
Fix the behavior of the boolean "attributes"
7b9d9ad
Change "spaces" to "when"
c9e9ded
Allow attributes to have their own config
9a8f800
Add a test case for a fixed bug
0f0ab21
Move the first option into the config object
There are 105 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | babel-core |
Current Version | 6.25.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | eslint-plugin-react |
Current Version | 7.2.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-react 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 ๐ช
forbid-prop-types
crash on identifiers (#1352 @ljharb)boolean-prop-naming
crash with propTypes wrapper (#1354 @dustinsoftware)prop-types
false positive with local variable props
(#1288 @DianaSuvorova)The new version differs by 11 commits.
8511835
Update CHANGELOG and bump version
0f6688b
Merge pull request #1124 from penx/patch-1
ecc5d89
Fix wrapped propTypes detection (fixes #1366)
4724d48
Merge pull request #1365 from DianaSuvorova/i1288
6272a1d
[prop types] fix an assignment to prop
b9bb564
Merge pull request #1358 from dustinsoftware/issue1354
99fd813
Fix propTypes wrapper crash in boolean-prop-naming
dae6574
[Tests] use pretest
to run the linter
2dcb73b
[Tests] fixup previous linter error
5ad93b4
[Fix] forbid-prop-types
: propWrapperFunctions breaks on identifiers.
08f451f
Update no-array-index-key.md to address issue 1123
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Hi, sorry if I'm overlooking something obvious but it seems that the suppressLocationOnMount option is not included in the typings file (index.d.ts).
Branch | Build failing ๐จ |
---|---|
Dependency | html-webpack-plugin |
Current Version | 2.29.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As html-webpack-plugin 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 ๐ช
The new version differs by 5 commits.
09a96f5
Release 2.30
cb15071
Uses a singleton cache to store the compilation stats (#723)
6f15d18
Add manual sort mode
bd043db
Change headReg and bodyReg to allow spaces (#709)
2cc10df
Release 2.29.0
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Is there any interest in supporting geolocation.watchPosition()
? It has a very similar API to getCurrentPosition() and it should be relatively painless to add support updating the component's state and de-registering the listener on componentWillUnmount.
Happy to take a stab at it if it's something you feel is appropriate for the lib.
Branch | Build failing ๐จ |
---|---|
Dependency | webpack-dev-server |
Current Version | 2.9.7 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
webpack-dev-server 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.
Version 2.10.0 adds the transpilation of the client scripts via babel to ES5 which restores backwards compatibility (that was removed in 2.8.0) to very old or out of date browsers.
Important webpack-dev-server has entered a maintenance-only mode. We won't be accepting any new features or major modifications. We'll still welcome pull requests for fixes however, and will continue to address any bugs that arise. Announcement with specifics pending.
reportTime
option (#1209)The new version differs by 13 commits.
ca8b5aa
2.10.0 (#1258)
17355f0
transpile client bundles with babel (#1242)
ce30460
rolling back webpack-dev-midddleware 2.0, as it's node6+
00e8500
updating deps and patching as necessary
082ddae
maint only mode
c9c61f2
fix(package): Increase minimum marked
version for ReDos vuln (#1255)
aab49de
iOS Safari 10 bug where SockJS couldn't be found (#1238)
a168b81
feat: reportTime
option (#1209)
32c3ceb
don't mutate stats configuration (#1174)
ef18fc8
Update sockjs dependency to fix auditjs security vulnerability warning (#1178)
7e89442
enable progress from config (#1181)
e8964d1
add --progress cli test (#1182)
a9327e5
Fix typos (#1236)
See the full diff
There is a collection of frequently asked questions. If those donโt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot ๐ด
I get this error when i use the modal in next.js starter (ssr), that have a npm-shrinkwrap.json file.
Branch | Build failing ๐จ |
---|---|
Dependency | babel-cli |
Current Version | 6.24.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-cli 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
As pointed out by @RishabhJain96 props are not being passed to the child component.
Related PR: #14
Branch | Build failing ๐จ |
---|---|
Dependency | babel-jest |
Current Version | 21.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-jest 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.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.
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 ๐ค
There is a collection of frequently asked questions. If those donโt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | webpack-dev-server |
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 webpack-dev-server 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 ๐ช
The new version differs by 6 commits.
62a46a5
2.7.0
ccd113a
Sockjs prefix config (#911)
1cf4359
add --allowed-hosts CLI option (#1012)
72efaab
Always allow requests with IP-address as host in checkHost() (#1007)
628f0a2
Fully mute output info if quiet is set to true. (#999)
8207238
Set undefined openPage to empty string when open option is true (#973)
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
16.4.14
to 16.4.15
.๐จ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@types/react 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.
There is a collection of frequently asked questions. If those donโt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot ๐ด
Hi,
in a Server Side Rendered Setup the component shows up a warning, regardless if client gets a position or not:
Warning: setState(...): Can only update a mounting component. This usually means you called setState() outside componentWillMount() on the server. This is a no-op. Please check the code for the Geolocated(MerchantSearch) component.
Can you check, if you can use the DOM before setting state?
Branch | Build failing ๐จ |
---|---|
Dependency | babel-register |
Current Version | 6.24.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-register 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | react-test-renderer |
Current Version | 15.6.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react-test-renderer 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
With the new support for master/docs
location for GitHub pages, it is no longer desirable to maintain the separate gh-pages
branch.
Also the demo page is not as clear as desired.
There is an error in the TypeScript typings that does not allow for Functional Stateless Component to be used.
Branch | Build failing ๐จ |
---|---|
Dependency | eslint |
Current Version | 4.4.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint 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 ๐ช
The new version differs by 3 commits.
0d9da6d
4.4.1
1ea9a6c
Build: changelog update for 4.4.1
ec93614
Fix: no-multi-spaces to avoid reporting consecutive tabs (fixes #9079) (#9087)
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
The boilerplate used to kick-start this repo is overly complex. Things to check:
05:57:12.132 Warning: Component's children should not be mutated.
in td (created by Demo)
in tr (created by Demo)
in tbody (created by Demo)
in table (created by Demo)
in Demo (created by Geolocated(Demo))
in Geolocated(Demo) (created by App)
in div (created by App)
in App1warning.js?:44:9warningwebpack:///./~/react/~/fbjs/lib/warning.js?:44:9handleElementwebpack:///./~/react/lib/ReactChildrenMutationWarningDevtool.js?:42:11ReactDOMUnknownPropertyDevtool.onComponentHasMountedwebpack:///./~/react/lib/ReactChildrenMutationWarningDevtool.js?:53:5emitEvent/<webpack:///./~/react/lib/ReactDebugTool.js?:30:9emitEventwebpack:///./~/react/lib/ReactDebugTool.js?:27:3ReactDebugTool.onComponentHasMountedwebpack:///./~/react/lib/ReactDebugTool.js?:254:5ReactDOMComponent.Mixin.mountComponent/callbackwebpack:///./~/react/lib/ReactDOMComponent.js?:574:18.notifyAllwebpack:///./~/react/lib/CallbackQueue.js?:67:9ON_DOM_READY_QUEUEING.closewebpack:///./~/react/lib/ReactReconcileTransaction.js?:81:5Mixin.closeAllwebpack:///./~/react/lib/Transaction.js?:204:11Mixin.performwebpack:///./~/react/lib/Transaction.js?:151:11Mixin.performwebpack:///./~/react/lib/Transaction.js?:138:13.performwebpack:///./~/react/lib/ReactUpdates.js?:90:12flushBatchedUpdateswebpack:///./~/react/lib/ReactUpdates.js?:173:7Mixin.closeAllwebpack:///./~/react/lib/Transaction.js?:204:11Mixin.performwebpack:///./~/react/lib/Transaction.js?:151:11ReactDefaultBatchingStrategy.batchedUpdateswebpack:///./~/react/lib/ReactDefaultBatchingStrategy.js?:63:7enqueueUpdatewebpack:///./~/react/lib/ReactUpdates.js?:201:5enqueueUpdatewebpack:///./~/react/lib/ReactUpdateQueue.js?:25:3ReactUpdateQueue.enqueueSetStatewebpack:///./~/react/lib/ReactUpdateQueue.js?:210:5ReactComponent.prototype.setStatewebpack:///./~/react/lib/ReactComponent.js?:64:3onPositionSuccesswebpack:///./~/react-geolocated/dist-modules/components/geolocated.js?:89:21componentDidMountwebpack:///./~/react-geolocated/dist-modules/components/geolocated.js?:102:21invokeComponentDidMountWithTimerwebpack:///./~/react/lib/ReactCompositeComponent.js?:60:3.notifyAllwebpack:///./~/react/lib/CallbackQueue.js?:67:9ON_DOM_READY_QUEUEING.closewebpack:///./~/react/lib/ReactReconcileTransaction.js?:81:5Mixin.closeAllwebpack:///./~/react/lib/Transaction.js?:204:11Mixin.performwebpack:///./~/react/lib/Transaction.js?:151:11batchedMountComponentIntoNodewebpack:///./~/react/lib/ReactMount.js?:126:3Mixin.performwebpack:///./~/react/lib/Transaction.js?:138:13ReactDefaultBatchingStrategy.batchedUpdateswebpack:///./~/react/lib/ReactDefaultBatchingStrategy.js?:63:7batchedUpdateswebpack:///./~/react/lib/ReactUpdates.js?:98:3ReactMount._renderNewRootComponentwebpack:///./~/react/lib/ReactMount.js?:285:5ReactMount._renderSubtreeIntoContainerwebpack:///./~/react/lib/ReactMount.js?:371:21ReactMount.renderwebpack:///./~/react/lib/ReactMount.js?:392:12<anonymous>webpack:///./src/index.js?:19:1<anonymous>http://localhost:3000/static/js/bundle.js:1318:2__webpack_require__http://localhost:3000/static/js/bundle.js:556:12hotCreateRequire/fnhttp://localhost:3000/static/js/bundle.js:87:20<anonymous>webpack:///multi_main?:4:18<anonymous>http://localhost:3000/static/js/bundle.js:589:2__webpack_require__http://localhost:3000/static/js/bundle.js:556:12<anonymous>http://localhost:3000/static/js/bundle.js:579:18<anonymous>http://localhost:3000/static/js/bundle.js:1:11
I was wondering if this component supports some sort of onLocationChange event which I could update my app's state with when the user changes location? Or would some sort of setInterval be the way to go?
Adding the code coverage tool (probably Coveralls) will help to maintain the code well tested.
First many thanks for this plugin! Great job :)
I do have one minor issue... The plugin seems to ask for permission on site load rather than waiting until someone has pressed a button that initiates this.props.isGeolocationAvailable. Anything I can do to get around this?
Branch | Build failing ๐จ |
---|---|
Dependency | semantic-release |
Current Version | 7.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As semantic-release 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 ๐ช
post: create v1.2.3
tag tag instead of branch (3f85597)
Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY
error :( To recover, follow these steps:
"version"
to what ever should have been released. As an example, let's say the new version number would be 1.2.3
. Save the changenpm publish
to release the new version. Make sure to run any pre-publish tasks first if you have anygit tag v1.2.3
(put in the same version as in step 2. Push the tag to GitHub with git push --tags
This will fix the problem and everything will work automagically again from here on now.
The new version differs by 1 commits.
0c79a9b
fix(post): create git tag properly
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | react |
Current Version | 15.6.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | react |
Current Version | 15.5.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
Hi,
Do you have an example for using it with nextjs? To me it looks like that it won't work. Thanks!
Hello,
This library works great on desktop, is there any way to make it work for ios and android devices? I tested on both and it doesn't seem to work.
Thanks!
react-geolocated/src/components/geolocated.js
Lines 92 to 96 in c342cdd
react-geolocated/src/components/geolocated.js
Lines 109 to 111 in c342cdd
this.watchId = funcPosition(
this.onPositionSuccess,
this.onPositionError,
positionOptions,
);
Branch | Build failing ๐จ |
---|---|
Dependency | babel-plugin-transform-object-rest-spread |
Current Version | 6.23.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-plugin-transform-object-rest-spread 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
I don't want the Lat Lng, I am not able to get the city name.
Branch | Build failing ๐จ |
---|---|
Dependency | react-dom |
Current Version | 15.6.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react-dom 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
There are libraries like typings-tester
, that could be used to replace the ad-hoc testing now in place.
master
branch failed. ๐จI recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iโm sure you can resolve this ๐ช.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donโt help, or if this issue is reporting something you think isnโt right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project โจ
Your semantic-release bot ๐ฆ๐
devDependency
react was updated from 16.6.1
to 16.6.2
.devDependency
react-dom was updated from 16.6.1
to 16.6.2
.devDependency
react-test-renderer was updated from 16.6.1
to 16.6.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 react group definition.
react 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.
There is a collection of frequently asked questions. If those donโt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot ๐ด
With TypeScript type definitions already included and Flow being available on Windows, it makes sense to add definitions for this as well.
There should also be some kind of tests to ensure the declarations are up-to-date (similarly as in #8).
Branch | Build failing ๐จ |
---|---|
Dependency | eslint |
Current Version | 4.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 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 ๐ช
node.start
/node.end
(fixes #8956) (#8984) (Toru Nagashima)indent
behavior on computed properties (fixes #8989) (#8999) (Teddy Katz)The new version differs by 33 commits.
a113cd3
4.4.0
181bd46
Build: changelog update for 4.4.0
89196fd
Upgrade: Espree to 3.5.0 (#9074)
b3e4598
Fix: clarify AST and don't use node.start
/node.end
(fixes #8956) (#8984)
62911e4
Update: Add ImportDeclaration option to indent rule (#8955)
de75f9b
Chore: enable object-curly-newline & object-property-newline.(fixes #9042) (#9068)
5ae8458
Docs: fix typo in object-shorthand.md (#9066)
c3d5b39
Docs: clarify options descriptions (fixes #8875) (#9060)
37158c5
Docs: clarified behavior of globalReturn option (fixes #8953) (#9058)
c2f3553
Docs: Update example for MemberExpression option of indent (fixes #9056) (#9057)
78a85e0
Fix: no-extra-parens incorrectly reports async function expressions (#9035)
c794f86
Fix: getter-return reporting method named 'get' (fixes #8919) (#9004)
d0f78ec
Docs: update rule deprecation policy (fixes #8635) (#9033)
5ab282f
Fix: Print error message in bin/eslint.js (fixes #9011) (#9041)
50e3cf3
Docs: Update sort-keys doc to define natural ordering (fixes #9043) (#9045)
There are 33 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
I would like there to be an option so that the browser prompt
does not appear right away, but instead as a result of a button click or any other user-generated action.
Can there be a function prop (with 3 callback arguments) that triggers the prompt being asked? Something like
function determineLocation() {
this.props.showLocationPrompt(this.allowed, this.blocked, this.closed)
}
function allowed() {
// user clicked allow (or had previously given permission to this site to access location)
}
function blocked(firstTime) {
if (firstTime) {
// user clicked the Block option
} else {
// attempt blocked because of prior blocking
}
}
function closed() {
// user chose neither Block or Allow, must have closed the prompt
}
For that blocked
function I think including a firstTime argument is necessary (not sure how to access it from browser settings though). When I was testing on localhost, I never saw the prompt to begin with, because it turns out I had previously blocked it and only found that out after looking at the site settings in Chrome:
Knowing whether the location request was blocked by clicking "Block" or due to prior clicking would allow for a more appropriate response message, such as "You have blocked access to location, unable to proceed" vs "You have previously blocked access to location. Please click on Site settings -> Location -> Always allow on this site." [slightly different message depending on the browser].
Branch | Build failing ๐จ |
---|---|
Dependency | css-loader |
Current Version | 0.28.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As css-loader 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 ๐ช
The new version differs by 10 commits.
e16bdeb
chore(release): 0.28.5
53283a1
chore: Update yarn lock file from #565
2e4ec09
fix: stricter @import
tolerance (#593)
b92c941
docs(README): Fix ExtractTextPlugin
example (#590)
3440d55
test: add test for escaped selector (#584)
eadbd47
docs(README): fix link (#579)
8dafee7
chore(package): update source-list-map v0.1.7...2.0.0
(dependencies
) (#565)
1fee601
fix: match mutliple dashes (options.camelCase
) (#556)
c13c467
docs(README): add localIdentName
to the options table (#551)
c2e0934
docs(README): fix broken link (#550)
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
16.7.22
to 16.8.0
.๐จ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@types/react 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.
There is a collection of frequently asked questions. If those donโt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot ๐ด
Branch | Build failing ๐จ |
---|---|
Dependency | react-dom |
Current Version | 15.5.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react-dom 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 ๐ช
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot ๐ด
When turning GPS on or off during operation, this.props.isGeolocationEnabled is not toggled in real-time, the change in GPS status props is only available after page reload.
Maybe do a debounce on the prop, but its only available within the child..
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.