Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change dependencies to peerDependencies #5142

Merged
merged 1 commit into from
Nov 24, 2016

Conversation

semeleven
Copy link
Contributor

If I some plugin include leaflet to dependencies and I have local version leaflet, then I have two version - leaflet from plugin and my.

If I some plugin include leaflet to dependencies and I have local version leaflet, then I have two version - leaflet from plugin and my.
@IvanSanchez IvanSanchez merged commit 1883620 into Leaflet:master Nov 24, 2016
@theashyster
Copy link
Contributor

I am confused now - so this was a wrong thing to do? #4534

@semone
Copy link

semone commented Nov 24, 2016

Plus one on the confusion

@theashyster
Copy link
Contributor

I would suggest the same thing as @hyperknot in #4534
If Leaflet is required for building a plugin, it should be specified in devDependencies, not peer.

DiogoMCampos pushed a commit to DiogoMCampos/Leaflet that referenced this pull request Dec 18, 2016
If I some plugin include leaflet to dependencies and I have local version leaflet, then I have two version - leaflet from plugin and my.
DiogoMCampos pushed a commit to DiogoMCampos/Leaflet that referenced this pull request Dec 18, 2016
If I some plugin include leaflet to dependencies and I have local version leaflet, then I have two version - leaflet from plugin and my.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants