clementallen / react-leaflet-semicircle Goto Github PK

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency react-leaflet was updated from 2.6.1 to 2.6.2.

🚨 View failing branch.

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

react-leaflet 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.

Your Greenkeeper Bot 🌴

Would it be possible to add React 18 support?

Peer dependencies seems to be outdated

I use
"react": "^16.13.1",
"react-leaflet": "^2.6.1",
"react-leaflet-semicircle": "^2.0.7".
This works fine in Google Chrome, but when you run the application in IE 11, you get error SCRIPT1028: SCRIPT1028: Expected identifier, string or number

There have been updates to the enzyme monorepo:

• • The devDependency enzyme-adapter-react-16 was updated from 1.9.1 to 1.10.0.

🚨 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 enzyme group definition.

enzyme 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.

Your Greenkeeper Bot 🌴

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency eslint-plugin-react was updated from 7.18.3 to 7.19.0.

🚨 View failing branch.

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

eslint-plugin-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.

Your Greenkeeper Bot 🌴

../node_modules/react-leaflet-semicircle/src/AbstractComponent.js
Module parse failed: Unexpected token (7:46)
You may need an appropriate loader to handle this file type.
| // props.leaflet is not used but destructured out so it's not passed to this.leafletComponent
| // eslint-disable-next-line no-unused-vars
| createLeafletElement({ position, leaflet, ...options }) {
| return new this.leafletComponent(position, options);
| }

When im trying to import the library i get this message!
Its versioning issue?
I have "react-leaflet-semicircle": "^2.0.6",
"react-leaflet": "^2.6.1",
"leaflet": "^1.6.0"
or i need to configure the webpack?

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Hi,

I have problem with updating the position of SemiCircle.

After the component has been initially rendered, I am updating using setState properties: position, stopAngle, startAngle. It works fine with angles, but not with the position, the marker stays on the initial position regardless of the value.

Any idea what the problem could be?

Here is the sample code: https://codesandbox.io/s/polished-grass-mtpr7
(Clicking big next button show iterate over positions to see the effect).

Thanks.

How can I submit path options to semi-circle such as fill color?

The devDependency leaflet was updated from 1.4.0 to 1.5.0.

🚨 View failing branch.

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

leaflet 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.

Your Greenkeeper Bot 🌴

This:

<Circle
  center={/*Some center*/}
  radius={/*Some radius*/}
>
  <Popup>
    Some description
  </Popup>
</Circle>

will work as expected: Popup will interact with the Circle component.

But this:

<SemiCircle
  position={/*Some center*/}
  radius={/*Some radius*/}
>
  <Popup>
    Some description
  </Popup>
</SemiCircle>

won't work as expected. As far as I know, Popup isn't receiving information from SemiCircle component. I don't know if this is intended, but having this feature would be great in order to have the same functionality with the other components.

The devDependency eslint was updated from 5.13.0 to 5.14.0.

🚨 View failing branch.

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

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

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

The devDependency eslint-plugin-react was updated from 7.14.0 to 7.14.1.

🚨 View failing branch.

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

eslint-plugin-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.

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

There have been updates to the babel7 monorepo:

• • The devDependency @babel/cli was updated from 7.7.7 to 7.8.0.

• The devDependency @babel/core was updated from 7.7.7 to 7.8.0.
• The devDependency @babel/preset-env was updated from 7.8.0 to 7.8.2.
• The devDependency @babel/preset-react was updated from 7.7.4 to 7.8.0.

🚨 View failing branch.

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

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

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

Your Greenkeeper Bot 🌴