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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Upgrade leaflet from 1.3.1 to 1.9.4 #4

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade leaflet from 1.3.1 to 1.9.4 #4

wants to merge 1 commit into from

Conversation

emdedeval
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade leaflet from 1.3.1 to 1.9.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 20 versions ahead of your current version.

  • The recommended version was released on a year ago.

Release notes
Package name: leaflet
  • 1.9.4 - 2023-05-18

    🐞 Bug fixes

    • Fix tile gaps in Chromium-based browsers (#8891 by @ IvanSanchez)
    • Fix vector drifts when zoomAnimation is false and zooming via flyTo or pinch (#8794 by @ plainheart)
    • Ensure toGeoJSON() still works with an empty array (#8737 by @ Falke-Design)
    • Ensure LineUtil and PolyUtil only iterate over array values and not properties (#8840 by @ Falke-Design)
    • Fix rounding errors in center calculation of LineUtil and PolyUtil for small layers (#8784 by @ Falke-Design)
    • Prevent unwanted layer toggle while expanding the Layers control on mobile (#8910 by @ Falke-Design)
    • Fix an error when a focusing on a Tooltip-bound FeatureGroup that contains a layer without a getElement method (#8890 by @ Falke-Design)
    • Fix Tooltip is not showing when loaded dynamically while moving the map (#8672 by @ theGOTOguy)
    • Fix noMoveStart option not applying to fitBounds (#8911 by @ AbdullahSohail-SE)
    • Fix outlines showing up when interacting with the map on Safari 16.4+ (#8917 by @ jonkoops)
  • 1.9.3 - 2022-11-18

    🙌 Accessibility

    • Expand the layers control on Enter keydown (#8556 by @ larsgw)
    • Align the scale control's alpha transparency with the attribution control (#8547 by @ Malvoz)
    • Allow the scale control's text to overflow the container (#8548 by @ Malvoz)

    🐞 Bug fixes

  • 1.9.2 - 2022-10-04

    🐞 Bug fixes

    • ⚠️ Drop ESM entrypoint from package because of numerous compatibility issues with plugins (import leaflet/dist/leaflet-src.esm.js explicitly instead to take advantage; ESM by default will come in v2) (#8493 by @ jonkoops)
    • Fix a bug where tooltips could throw an error with canvas renderer (#8498 by @ Falke-Design)
    • Fix a bug with incorrect marker popup location when there are multiple markers registered to the same popup (#8523 by @ raychanks).

    🧪 Tests

    • Fix unit tests suite stopping abruptly on Mac (#8478)

    📝 Docs

  • 1.9.1 - 2022-09-23
    • Fix Events listens not propagating to parent objects, in particular fixing compatibility with Leaflet.markercluster plugin (#8211 by @ Falke-Design)
  • 1.9.0 - 2022-09-22

    ⚡ Note on future versions

    The v1.9 release is setting the stage for the first major version bump of Leaflet since 2016! A lot has changed since then, and it's time for Leaflet to grow together with the web platform.

    After this release, we are branching off the 1.x code and putting it in maintenance mode — reserving potential 1.x releases only for critical bugfixes. Although version 2.0 is still far away and will take some time to take shape, we plan to make the following changes:

    • Dropping support for Internet Explorer.
      This has been a long time coming, but now that Internet Explorer is officially end-of-life, it's time to say goodbye. Going forward, Leaflet will move to an evergreen strategy that targets browsers like Firefox, Chrome, Edge and Safari.
    • Embracing modern JavaScript.
      To maintain backwards compatibility, Leaflet is written entirely in ES5, a version of JavaScript supported by legacy browsers. So we have not been able to make use of many great JavaScript features (e.g. standardized classes, instead having to rely on our own implementation). By adopting a more modern version of the ECMAScript standard, we can start working towards aligning Leaflet with what is expected from a modern JavaScript library.
    • Standardized modules.
      When we released Leaflet v1, the landscape in the JavaScript world was very different and full of competing module standards such as CommonJS, AMD and UMD. Today, ECMAScript modules have become the clear way forward to unite the JavaScript ecosystem under one banner. Moving forward, Leaflet will only be distributed in a single standardized module system, greatly reducing complexity of our distributed code.
    • Removing the Leaflet global.
      As a developer using Leaflet, the capital letter L is probably intimately familiar to you. This is the Leaflet global where all of Leaflet's functionality lives. To allow compiler tooling to better eliminate dead-code through a process called tree-shaking, we are removing this global variable. To preserve backwards compatibility with older plugins, we will provide a shim that can be imported manually that will restore this functionality.

    v1.9.0 changelog

    ⚠️ Breaking Changes

    • (This change has been reverted in v1.9.2) Expose ESM entrypoint with Leaflet global (#8329 by @ jonkoops).
    • Update color-adjust to print-color-adjust (#8211 by @ Malvoz)

    ❇️ API changes

    ✨ Improvements

    🙌 Accessibility

    🐞 Bug fixes

    📝 Docs

    🔧 Workflow

    🧪 Tests

    v1.9.x updates:

    We've since released:

    • v1.9.1 to address compatibility with Leaflet.markercluster plugin.
    • v1.9.2 to fix ESM compatibility issues with other plugins, and fix and issue tooltips & canvas renderer.

    Stand With Ukraine

  • 1.8.0 - 2022-04-18

    v1.8.0 is a culmination of 1.5 years of development, a huge release focused on bug fixes, major reliability and accessibility improvements, cleaning up legacy code, and numerous improvements to documentation, development workflow and release process. A culmination of hundreds of contributions, and a preparation for bigger changes to come. 🍃

    I'm making this release just as an air raid alert is sounding outside, in Kyiv, warning about an imminent Russian air strike. This release is dedicated to Ukrainian fight for freedom and democracy against the Russian invasion 🇺🇦 (see how you can support Ukraine here).

    From now on, releases will become much more frequent. Thanks to our amazing community for all your help and patience. ❤️🙏 Special thanks to @ johnd0e who revived Leaflet development after long stagnation and made the biggest contributions, @ Falke-Design for doing the bulk of the work organizing development and preparing the release, @ Malvoz for his numerous accessibility contributions, and @ jonkoops for help with workflow automations. ❤️

    ⚠️ Breaking Changes

    • Improve reliability of contextmenu event simulation on mobile Safari by introducing a new TapHold handler, replacing legacy Tap (#7026 by @ johnd0e)
    • Reorganize DivOverlay/Popup/Tooltip APIs (#7540 by @ johnd0e)
    • Improve error / argument handling for event listeners (#7518 by @ johnd0e)
    • Improve reliability of touch events simulation on non-touch devices (DomEvent.Pointer) (#7059, #7084, #7415 by @ johnd0e)
    • Improve reliability of dblclick event simulation on touch devices (DomEvent.DoubleTap) (#7027 by @ johnd0e)
    • Improve reliability of disableClickPropagation (#7439 by @ johnd0e)
    • Improve Map hasLayer() and LayerGroup hasLayer() to require a layer as argument (#6999 by @ johnd0e)
    • Fix Class.include to not overwrite options (#7756 by @ johnd0e)
    • Fix Class.extend to not modify source props object (#6766 by @ johnd0e)
    • Improve Browser.touch touch devices detection (#7029 by @ johnd0e)
    • Get rid of legacy Android hacks (#7022 by @ johnd0e)
    • Allow fonts to respect users' browser settings by making the font-size relative to the map container. (You can change the font size on leaflet-container to adjust it if needed.) (#7800 by @ Chandu-4444)

    ❇️ API changes

    ✨ Improvements

    • Improve memory footprint by removing will-change CSS property on tile images (#7872 by @ janjaap)
    • Improve reliability of icons path detection heuristics (#7092 by @ johnd0e)
    • Improve performance of adding tiled sources by avoiding excessive updates in GridLayer.onAdd (#7570 by @ johnd0e)
    • Improve handling of edge cases in panInside (#7469 by @ daverayment)
    • Minify marker icon SVG (#7600 by @ rala72)
    • Allow template keys with spaces in TileLayer URL (#7216 by @ lubojr)
    • Improve behavior of Tooltip bound to ImageOverlay (#7306 by @ IvanSanchez)
    • Remove the gap between Popup tip and content dialog (#7920 by @ Malvoz)
    • Fire mousemove through Canvas to map if it has no layers (#7809 by @ johnd0e)
    • Add print styles to prevent printers from removing background-images in controls (#7851 by @ Malvoz)
    • Move attribution code from Layer to Control.Attribution (#7764 by @ johnd0e)
    • Refactor vmlCreate() so that it does not expose closure to TypeError (#7279 by @ darcyparker)
    • Improve reliability of Control.Layers by not relying on Browser android and touch properties (#7057 by @ johnd0e)
    • Improve reliability of Tooltip by not relying on Browser touch checks (

@snyk-bot
fix: upgrade leaflet from 1.3.1 to 1.9.4
3c44c14 
Snyk has created this PR to upgrade leaflet from 1.3.1 to 1.9.4.

See this package in npm:
leaflet

See this project in Snyk:
https://app.snyk.io/org/emdedeval/project/4047af54-aa4c-4d42-83de-167e135bf796?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@emdedeval @snyk-bot