For a quick demo app and easy code samples, check out the plugin page at the Verified Plugins Marketplace: http://plugins.telerik.com/plugin/calendar
\n
\n
\n\n1. [Description](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#1-description)\n2. [Installation](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#2-installation)\n\t2. [Automatically](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#automatically)\n\t2. [Manually](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#manually)\n\t2. [PhoneGap Build](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#phonegap-build)\n3. [Usage](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#3-usage)\n4. [Promises](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#4-promises)\n5. [Credits](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#5-credits)\n6. [License](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin#6-license)\n\n## 1. Description\n\nThis plugin allows you to add events to the Calendar of the mobile device.\n\n* Works with PhoneGap >= 3.0.\n* For PhoneGap 2.x, see [the pre-3.0 branch](https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin/tree/pre-3.0).\n* Compatible with [Cordova Plugman](https://github.com/apache/cordova-plugman).\n* [Officially supported by PhoneGap Build](https://build.phonegap.com/plugins).\n\n### iOS specifics\n* Supported methods: `find`, `create`, `modify`, `delete`, ..\n* All methods work without showing the native calendar. Your app never loses control.\n* Tested on iOS 6+.\n* On iOS 10+ you need to provide a reason to the user for Calendar access. This plugin adds an empty `NSCalendarsUsageDescription` key to the /platforms/ios/*-Info.plist file which you can override with your custom string. To do so, pass the following variable when installing the plugin:\n\n```\ncordova plugin add cordova-plugin-calendar --variable CALENDAR_USAGE_DESCRIPTION=\"This app uses your calendar\"\n```\n\n### Android specifics\n* Supported methods on Android 4: `find`, `create` (silent and interactive), `delete`, ..\n* Supported methods on Android 2 and 3: `create` interactive only: the user is presented a prefilled Calendar event. Pressing the hardware back button will give control back to your app.\n\n### Windows 10 Mobile\n* Supported methods: `createEvent`, `createEventWithOptions`, `createEventInteractively`, `createEventInteractivelyWithOptions` only interactively\n\n## 2. Installation\n\n### Automatically\nLatest release on npm:\n```\n$ cordova plugin add cordova-plugin-calendar\n```\n\nBleeding edge, from github:\n```\n$ cordova plugin add https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin.git\n```\n\n### Manually\n\n#### iOS\n\n1\\. Add the following xml to your `config.xml`:\n```xml\n\n\n\t\n\n```\n\n2\\. Grab a copy of Calendar.js, add it to your project and reference it in `index.html`:\n```html\n\n```\n\n3\\. Download the source files for iOS and copy them to your project.\n\nCopy `Calendar.h` and `Calendar.m` to `platforms/ios//Plugins`\n\n4\\. Click your project in XCode, Build Phases, Link Binary With Libraries, search for and add `EventKit.framework` and `EventKitUI.framework`.\n\n#### Android\n\n1\\. Add the following xml to your `config.xml`:\n```xml\n\n\n \n\n```\n\n2\\. Grab a copy of Calendar.js, add it to your project and reference it in `index.html`:\n```html\n\n```\n\n3\\. Download the source files for Android and copy them to your project.\n\nAndroid: Copy `Calendar.java` to `platforms/android/src/nl/xservices/plugins` (create the folders/packages).\nThen create a package called `accessor` and copy other 3 java Classes into it.\n\n4\\. Add these permissions to your AndroidManifest.xml:\n```xml\n\n\n```\n\nNote that if you don't want your app to ask for these permissions, you can leave them out, but you'll only be able to\nuse one function of this plugin: `createEventInteractively`.\n\n\n### PhoneGap Build\n\nAdd the following xml to your `config.xml` to always use the latest npm version of this plugin:\n```xml\n\n```\n\nAlso, make sure you're building with Gradle by adding this to your `config.xml` file:\n```xml\n\n```\n\n## 3. Usage\n\nThe table gives an overview of basic operation compatibility:\n\nOperation | Comment | iOS | Android | Windows |\n----------------------------------- | ----------- | --- | ------- | ------- |\ncreateCalendar | | yes | yes | |\ndeleteCalendar | | yes | yes | |\ncreateEvent | silent | yes | yes * | yes ** |\ncreateEventWithOptions | silent | yes | yes * | yes ** |\ncreateEventInteractively | interactive | yes | yes | yes ** |\ncreateEventInteractivelyWithOptions | interactive | yes | yes | yes ** |\nfindEvent | | yes | yes | |\nfindEventWithOptions | | yes | yes | |\nlistEventsInRange | | yes | yes | |\nlistCalendars | | yes | yes | |\nfindAllEventsInNamedCalendars | | yes | | |\nmodifyEvent | | yes | | |\nmodifyEventWithOptions | | yes | | |\ndeleteEvent | | yes | yes | |\ndeleteEventFromNamedCalendar | | yes | | |\ndeleteEventById | | yes | yes | |\nopenCalendar | | yes | yes | |\n\n* \\* on Android < 4 dialog is shown\n* \\** only interactively on windows mobile\n\nBasic operations, you'll want to copy-paste this for testing purposes:\n```js\n // prep some variables\n var startDate = new Date(2015,2,15,18,30,0,0,0); // beware: month 0 = january, 11 = december\n var endDate = new Date(2015,2,15,19,30,0,0,0);\n var title = \"My nice event\";\n var eventLocation = \"Home\";\n var notes = \"Some notes about this event.\";\n var success = function(message) { alert(\"Success: \" + JSON.stringify(message)); };\n var error = function(message) { alert(\"Error: \" + message); };\n\n // create a calendar (iOS only for now)\n window.plugins.calendar.createCalendar(calendarName,success,error);\n // if you want to create a calendar with a specific color, pass in a JS object like this:\n var createCalOptions = window.plugins.calendar.getCreateCalendarOptions();\n createCalOptions.calendarName = \"My Cal Name\";\n createCalOptions.calendarColor = \"#FF0000\"; // an optional hex color (with the # char), default is null, so the OS picks a color\n window.plugins.calendar.createCalendar(createCalOptions,success,error);\n\n // delete a calendar\n window.plugins.calendar.deleteCalendar(calendarName,success,error);\n\n // create an event silently (on Android < 4 an interactive dialog is shown)\n window.plugins.calendar.createEvent(title,eventLocation,notes,startDate,endDate,success,error);\n\n // create an event silently (on Android < 4 an interactive dialog is shown which doesn't use this options) with options:\n var calOptions = window.plugins.calendar.getCalendarOptions(); // grab the defaults\n calOptions.firstReminderMinutes = 120; // default is 60, pass in null for no reminder (alarm)\n calOptions.secondReminderMinutes = 5;\n\n // Added these options in version 4.2.4:\n calOptions.recurrence = \"monthly\"; // supported are: daily, weekly, monthly, yearly\n calOptions.recurrenceEndDate = new Date(2016,10,1,0,0,0,0,0); // leave null to add events into infinity and beyond\n calOptions.calendarName = \"MyCreatedCalendar\"; // iOS only\n calOptions.calendarId = 1; // Android only, use id obtained from listCalendars() call which is described below. This will be ignored on iOS in favor of calendarName and vice versa. Default: 1.\n\n // This is new since 4.2.7:\n calOptions.recurrenceInterval = 2; // once every 2 months in this case, default: 1\n\n // And the URL can be passed since 4.3.2 (will be appended to the notes on Android as there doesn't seem to be a sep field)\n calOptions.url = \"https://www.google.com\";\n\n // on iOS the success handler receives the event ID (since 4.3.6)\n window.plugins.calendar.createEventWithOptions(title,eventLocation,notes,startDate,endDate,calOptions,success,error);\n\n // create an event interactively\n window.plugins.calendar.createEventInteractively(title,eventLocation,notes,startDate,endDate,success,error);\n\n // create an event interactively with the calOptions object as shown above\n window.plugins.calendar.createEventInteractivelyWithOptions(title,eventLocation,notes,startDate,endDate,calOptions,success,error);\n\n // create an event in a named calendar (iOS only, deprecated, use createEventWithOptions instead)\n window.plugins.calendar.createEventInNamedCalendar(title,eventLocation,notes,startDate,endDate,calendarName,success,error);\n\n // find events (on iOS this includes a list of attendees (if any))\n window.plugins.calendar.findEvent(title,eventLocation,notes,startDate,endDate,success,error);\n\n // if you need to find events in a specific calendar, use this one. All options are currently ignored when finding events, except for the calendarName.\n var calOptions = window.plugins.calendar.getCalendarOptions();\n calOptions.calendarName = \"MyCreatedCalendar\"; // iOS only\n calOptions.id = \"D9B1D85E-1182-458D-B110-4425F17819F1\"; // if not found, we try matching against title, etc\n window.plugins.calendar.findEventWithOptions(title,eventLocation,notes,startDate,endDate,calOptions,success,error);\n\n // list all events in a date range (only supported on Android for now)\n window.plugins.calendar.listEventsInRange(startDate,endDate,success,error);\n\n // list all calendar names - returns this JS Object to the success callback: [{\"id\":\"1\", \"name\":\"first\"}, ..]\n window.plugins.calendar.listCalendars(success,error);\n\n // find all _future_ events in the first calendar with the specified name (iOS only for now, this includes a list of attendees (if any))\n window.plugins.calendar.findAllEventsInNamedCalendar(calendarName,success,error);\n\n // change an event (iOS only for now)\n var newTitle = \"New title!\";\n window.plugins.calendar.modifyEvent(title,eventLocation,notes,startDate,endDate,newTitle,eventLocation,notes,startDate,endDate,success,error);\n\n // or to add a reminder, make it recurring, change the calendar, or the url, use this one:\n var filterOptions = window.plugins.calendar.getCalendarOptions(); // or {} or null for the defaults\n filterOptions.calendarName = \"Bla\"; // iOS only\n filterOptions.id = \"D9B1D85E-1182-458D-B110-4425F17819F1\"; // iOS only, get it from createEventWithOptions (if not found, we try matching against title, etc)\n var newOptions = window.plugins.calendar.getCalendarOptions();\n newOptions.calendaName = \"New Bla\"; // make sure this calendar exists before moving the event to it\n // not passing in reminders will wipe them from the event. To wipe the default first reminder (60), set it to null.\n newOptions.firstReminderMinutes = 120;\n window.plugins.calendar.modifyEventWithOptions(title,eventLocation,notes,startDate,endDate,newTitle,eventLocation,notes,startDate,endDate,filterOptions,newOptions,success,error);\n\n // delete an event (you can pass nulls for irrelevant parameters). The dates are mandatory and represent a date range to delete events in.\n // note that on iOS there is a bug where the timespan must not be larger than 4 years, see issue 102 for details.. call this method multiple times if need be\n // since 4.3.0 you can match events starting with a prefix title, so if your event title is 'My app - cool event' then 'My app -' will match.\n window.plugins.calendar.deleteEvent(newTitle,eventLocation,notes,startDate,endDate,success,error);\n\n // delete an event, as above, but for a specific calendar (iOS only)\n window.plugins.calendar.deleteEventFromNamedCalendar(newTitle,eventLocation,notes,startDate,endDate,calendarName,success,error);\n\n // delete an event by id. If the event has recurring instances, all will be deleted unless `fromDate` is specified, which will delete from that date onward. (iOS and android only)\n window.plugins.calendar.deleteEventById(id,fromDate,success,error);\n\n // open the calendar app (added in 4.2.8):\n // - open it at 'today'\n window.plugins.calendar.openCalendar();\n // - open at a specific date, here today + 3 days\n var d = new Date(new Date().getTime() + 3*24*60*60*1000);\n window.plugins.calendar.openCalendar(d, success, error); // callbacks are optional\n```\n\nCreating an all day event:\n```js\n // set the startdate to midnight and set the enddate to midnight the next day\n var startDate = new Date(2014,2,15,0,0,0,0,0);\n var endDate = new Date(2014,2,16,0,0,0,0,0);\n```\n\nCreating an event for 3 full days\n```js\n // set the startdate to midnight and set the enddate to midnight 3 days later\n var startDate = new Date(2014,2,24,0,0,0,0,0);\n var endDate = new Date(2014,2,27,0,0,0,0,0);\n```\n\nExample Response IOS getCalendarOptions\n```js\n{\ncalendarId: null,\ncalendarName: \"calendar\",\nfirstReminderMinutes: 60,\nrecurrence: null,\nrecurrenceEndDate: null,\nrecurrenceInterval: 1,\nsecondReminderMinutes: null,\nurl: null\n}\n```\n\nExmaple Response IOS Calendars\n```js\n{\nid: \"258B0D99-394C-4189-9250-9488F75B399D\",\nname: \"standard calendar\",\ntype: \"Local\"\n}\n```\n\nExmaple Response IOS Event\n```js\n{\ncalendar: \"Kalender\",\nendDate: \"2016-06-10 23:59:59\",\nid: \"0F9990EB-05A7-40DB-B082-424A85B59F90\",\nlastModifiedDate: \"2016-06-13 09:14:02\",\nlocation: \"\",\nmessage: \"my description\",\nstartDate: \"2016-06-10 00:00:00\",\ntitle: \"myEvent\"\n}\n```\n\n### Android 6 (M) Permissions\nOn Android 6 you need to request permission to use the Calendar at runtime when targeting API level 23+.\nEven if the `uses-permission` tags for the Calendar are present in `AndroidManifest.xml`.\n\nSince plugin version 4.5.0 we transparently handle this for you in a just-in-time manner.\nSo if you call `createEvent` we will pop up the permission dialog. After the user granted access\nto his calendar the event will be created.\n\nYou can also manually manage and check permissions if that's your thing.\nNote that the hasPermission functions will return true when:\n\n- You're running this on iOS, or\n- You're targeting an API level lower than 23, or\n- You're using Android < 6, or\n- You've already granted permission.\n\n```js\n // again, this is no longer needed with plugin version 4.5.0 and up\n function hasReadWritePermission() {\n window.plugins.calendar.hasReadWritePermission(\n function(result) {\n // if this is 'false' you probably want to call 'requestReadWritePermission' now\n alert(result);\n }\n )\n }\n\n function requestReadWritePermission() {\n // no callbacks required as this opens a popup which returns async\n window.plugins.calendar.requestReadWritePermission();\n }\n```\n\nThere are similar methods for Read and Write access only (`hasReadPermission`, etc),\nalthough it looks like that if you request read permission you can write as well,\nso you might as well stick with the example above.\n\nNote that backward compatibility was added by checking for read or write permission in the relevant plugins functions.\nIf permission is needed the plugin will now show the permission request popup.\nThe user will then need to allow access and invoke the same method again after doing so.\n\n## 4. Promises\nIf you like to use promises instead of callbacks, or struggle to create a lot of\nevents asynchronously with this plugin then I encourage you to take a look at\n[this awesome wrapper](https://github.com/poetic-labs/native-calender-api) for\nthis plugin. Kudos to [John Rodney](https://github.com/JohnRodney) for this piece of art!\n\n## 5. Credits\n\nThis plugin was enhanced for Plugman / PhoneGap Build by [Eddy Verbruggen](http://www.x-services.nl). I fixed some issues in the native code (mainly for iOS) and changed the JS-Native functions a little in order to make a universal JS API for both platforms.\n* Inspired by [this nice blog of Devgirl](http://devgirl.org/2013/07/17/tutorial-how-to-write-a-phonegap-plugin-for-android/).\n* Credits for the original iOS code go to [Felix Montanez](https://github.com/felixactv8/Phonegap-Calendar-Plugin-ios).\n* Credits for the original Android code go to [Ten Forward Consulting](https://github.com/tenforwardconsulting/Phonegap-Calendar-Plugin-android) and [twistandshout](https://github.com/twistandshout/phonegap-calendar-plugin).\n* Special thanks to [four32c.com](http://four32c.com) for sponsoring part of the implementation, while keeping the plugin opensource.\n\n## 6. License\n\n[The MIT License (MIT)](http://www.opensource.org/licenses/mit-license.html)\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n",
"name": "cordova-plugin-calendar@5.1.6",
"licenses": "MIT",
"repository": "https://github.com/EddyVerbruggen/Calendar-PhoneGap-Plugin",
"publisher": "Eddy Verbruggen",
"email": "eddyverbruggen@gmail.com",
"url": "https://github.com/EddyVerbruggen"
},
{
"licenseText": "The MIT License (MIT)\n\nCopyright (c) 2012 James Halliday, Josh Duff, and other contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n",
"name": "deepmerge@4.2.2",
"licenses": "MIT",
"repository": "https://github.com/TehShrike/deepmerge"
},
{
"licenseText": "Copyright (c) 2012 Felix Geisendörfer (felix@debuggable.com) and contributors\n\n Permission is hereby granted, free of charge, to any person obtaining a copy\n of this software and associated documentation files (the \"Software\"), to deal\n in the Software without restriction, including without limitation the rights\n to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n copies of the Software, and to permit persons to whom the Software is\n furnished to do so, subject to the following conditions:\n\n The above copyright notice and this permission notice shall be included in\n all copies or substantial portions of the Software.\n\n THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\n AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\n THE SOFTWARE.\n",
"name": "form-data@4.0.0",
"licenses": "MIT",
"repository": "https://github.com/form-data/form-data",
"publisher": "Felix Geisendörfer",
"email": "felix@debuggable.com",
"url": "http://debuggable.com/"
},
{
"licenseText": "Copyright 2016 Casey Thomas\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n",
"name": "geojson@0.5.0",
"licenses": "MIT",
"repository": "https://github.com/caseycesari/geojson.js",
"publisher": "Casey Cesari"
},
{
"licenseText": "MIT License\n\nCopyright (c) 2019 Wi3land\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n",
"name": "ionic-appauth@0.9.0",
"licenses": "MIT",
"repository": "https://github.com/wi3land/ionic-appauth",
"publisher": "wi3land"
},
{
"licenseText": "The MIT License (MIT)\n\nCopyright (c) 2011-2019 Stefan Goessner, Subbu Allamaraju, Mike Brevoort,\nRobert Krahn, Brett Zamir, Richard Schneider\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n",
"name": "jsonpath-plus@6.0.1",
"licenses": "MIT",
"repository": "https://github.com/s3u/JSONPath",
"publisher": "Stefan Goessner"
},
{
"licenseText": "Leaflet.markercluster\n=====================\n\nProvides Beautiful Animated Marker Clustering functionality for [Leaflet](http://leafletjs.com), a JS library for interactive maps.\n\n*Requires Leaflet 1.0.0*\n\n\n\nFor a Leaflet 0.7 compatible version, [use the leaflet-0.7 branch](https://github.com/Leaflet/Leaflet.markercluster/tree/leaflet-0.7) \nFor a Leaflet 0.5 compatible version, [Download b128e950](https://github.com/Leaflet/Leaflet.markercluster/archive/b128e950d8f5d7da5b60bd0aa9a88f6d3dd17c98.zip) \nFor a Leaflet 0.4 compatible version, [Download the 0.2 release](https://github.com/Leaflet/Leaflet.markercluster/archive/0.2.zip)\n\n\n## Table of Contents\n * [Using the plugin](#using-the-plugin)\n * [Building, testing and linting scripts](#building-testing-and-linting-scripts)\n * [Examples](#examples)\n * [Usage](#usage)\n * [Options](#options)\n * [Defaults](#defaults)\n * [Customising the Clustered Markers](#customising-the-clustered-markers)\n * [Customising Spiderfy shape positions](#customising-spiderfy-shape-positions)\n * [All Options](#all-options)\n * [Enabled by default (boolean options)](#enabled-by-default-boolean-options)\n * [Other options](#other-options)\n * [Chunked addLayers options](#chunked-addlayers-options)\n * [Events](#events)\n * [Additional MarkerClusterGroup Events](#additional-markerclustergroup-events)\n * [Methods](#methods)\n * [Group methods](#group-methods)\n * [Adding and removing Markers](#adding-and-removing-markers)\n * [Bulk adding and removing Markers](#bulk-adding-and-removing-markers)\n * [Getting the visible parent of a marker](#getting-the-visible-parent-of-a-marker)\n * [Refreshing the clusters icon](#refreshing-the-clusters-icon)\n * [Other Group Methods](#other-group-methods)\n * [Clusters methods](#clusters-methods)\n * [Getting the bounds of a cluster](#getting-the-bounds-of-a-cluster)\n * [Zooming to the bounds of a cluster](#zooming-to-the-bounds-of-a-cluster)\n * [Other clusters methods](#other-clusters-methods)\n * [Handling LOTS of markers](#handling-lots-of-markers)\n * [License](#license)\n * [Sub-plugins](#sub-plugins)\n\n\n## Using the plugin\nInclude the plugin CSS and JS files on your page after Leaflet files, using your method of choice:\n* [Download the `v1.4.1` release](https://github.com/Leaflet/Leaflet.markercluster/archive/v1.4.1.zip)\n* Use unpkg CDN: `https://unpkg.com/leaflet.markercluster@1.4.1/dist/`\n* Install with npm: `npm install leaflet.markercluster`\n\nIn each case, use files in the `dist` folder:\n* `MarkerCluster.css`\n* `MarkerCluster.Default.css` (not needed if you use your own `iconCreateFunction` instead of the default one)\n* `leaflet.markercluster.js` (or `leaflet.markercluster-src.js` for the non-minified version)\n\n### Building, testing and linting scripts\nInstall jake `npm install -g jake` then run `npm install`\n* To check the code for errors and build Leaflet from source, run `jake`.\n* To run the tests, run `jake test`.\n\n### Examples\nSee the included examples for usage.\n\nThe [realworld example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.388.html) is a good place to start, it uses all of the defaults of the clusterer.\nOr check out the [custom example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-custom.html) for how to customise the behaviour and appearance of the clusterer\n\n### Usage\nCreate a new MarkerClusterGroup, add your markers to it, then add it to the map\n\n```javascript\nvar markers = L.markerClusterGroup();\nmarkers.addLayer(L.marker(getRandomLatLng(map)));\n... Add more layers ...\nmap.addLayer(markers);\n```\n\n## Options\n### Defaults\nBy default the Clusterer enables some nice defaults for you:\n* **showCoverageOnHover**: When you mouse over a cluster it shows the bounds of its markers.\n* **zoomToBoundsOnClick**: When you click a cluster we zoom to its bounds.\n* **spiderfyOnMaxZoom**: When you click a cluster at the bottom zoom level we spiderfy it so you can see all of its markers. (*Note: the spiderfy occurs at the current zoom level if all items within the cluster are still clustered at the maximum zoom level or at zoom specified by `disableClusteringAtZoom` option*)\n* **removeOutsideVisibleBounds**: Clusters and markers too far from the viewport are removed from the map for performance.\n* **spiderLegPolylineOptions**: Allows you to specify [PolylineOptions](http://leafletjs.com/reference.html#polyline-options) to style spider legs. By default, they are `{ weight: 1.5, color: '#222', opacity: 0.5 }`.\n\nYou can disable any of these as you want in the options when you create the MarkerClusterGroup:\n```javascript\nvar markers = L.markerClusterGroup({\n\tspiderfyOnMaxZoom: false,\n\tshowCoverageOnHover: false,\n\tzoomToBoundsOnClick: false\n});\n```\n\n### Customising the Clustered Markers\nAs an option to MarkerClusterGroup you can provide your own function for creating the Icon for the clustered markers.\nThe default implementation changes color at bounds of 10 and 100, but more advanced uses may require customising this.\nYou do not need to include the .Default css if you go this way.\nYou are passed a MarkerCluster object, you'll probably want to use `getChildCount()` or `getAllChildMarkers()` to work out the icon to show.\n\n```javascript\nvar markers = L.markerClusterGroup({\n\ticonCreateFunction: function(cluster) {\n\t\treturn L.divIcon({ html: '' + cluster.getChildCount() + '' });\n\t}\n});\n```\n\nCheck out the [custom example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-custom.html) for an example of this.\n\nIf you need to update the clusters icon (e.g. they are based on markers real-time data), use the method [refreshClusters()](#refreshing-the-clusters-icon).\n\n### Customising Spiderfy shape positions\nYou can also provide a custom function as an option to MarkerClusterGroup to override the spiderfy shape positions. The example below implements linear spiderfy positions which overrides the default circular shape.\n\n```javascript\nvar markers = L.markerClusterGroup({\n\tspiderfyShapePositions: function(count, centerPt) {\n var distanceFromCenter = 35,\n markerDistance = 45,\n lineLength = markerDistance * (count - 1),\n lineStart = centerPt.y - lineLength / 2,\n res = [],\n i;\n\n res.length = count;\n\n for (i = count - 1; i >= 0; i--) {\n res[i] = new Point(centerPt.x + distanceFromCenter, lineStart + markerDistance * i);\n }\n\n return res;\n }\n});\n```\n\n### All Options\n#### Enabled by default (boolean options)\n* **showCoverageOnHover**: When you mouse over a cluster it shows the bounds of its markers.\n* **zoomToBoundsOnClick**: When you click a cluster we zoom to its bounds.\n* **spiderfyOnMaxZoom**: When you click a cluster at the bottom zoom level we spiderfy it so you can see all of its markers. (*Note: the spiderfy occurs at the current zoom level if all items within the cluster are still clustered at the maximum zoom level or at zoom specified by `disableClusteringAtZoom` option*).\n* **removeOutsideVisibleBounds**: Clusters and markers too far from the viewport are removed from the map for performance.\n* **animate**: Smoothly split / merge cluster children when zooming and spiderfying. If `L.DomUtil.TRANSITION` is false, this option has no effect (no animation is possible).\n\n#### Other options\n* **animateAddingMarkers**: If set to true (and `animate` option is also true) then adding individual markers to the MarkerClusterGroup after it has been added to the map will add the marker and animate it into the cluster. Defaults to false as this gives better performance when bulk adding markers. addLayers does not support this, only addLayer with individual Markers.\n* **disableClusteringAtZoom**: If set, at this zoom level and below, markers will not be clustered. This defaults to disabled. [See Example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld-maxzoom.388.html). Note: you may be interested in disabling `spiderfyOnMaxZoom` option when using `disableClusteringAtZoom`.\n* **maxClusterRadius**: The maximum radius that a cluster will cover from the central marker (in pixels). Default 80. Decreasing will make more, smaller clusters. You can also use a function that accepts the current map zoom and returns the maximum cluster radius in pixels.\n* **polygonOptions**: Options to pass when creating the L.Polygon(points, options) to show the bounds of a cluster. Defaults to empty, which lets Leaflet use the [default Path options](http://leafletjs.com/reference.html#path-options).\n* **singleMarkerMode**: If set to true, overrides the icon for all added markers to make them appear as a 1 size cluster. Note: the markers are not replaced by cluster objects, only their icon is replaced. Hence they still react to normal events, and option `disableClusteringAtZoom` does not restore their previous icon (see [#391](https://github.com/Leaflet/Leaflet.markercluster/issues/391)).\n* **spiderLegPolylineOptions**: Allows you to specify [PolylineOptions](http://leafletjs.com/reference.html#polyline-options) to style spider legs. By default, they are `{ weight: 1.5, color: '#222', opacity: 0.5 }`.\n* **spiderfyDistanceMultiplier**: Increase from 1 to increase the distance away from the center that spiderfied markers are placed. Use if you are using big marker icons (Default: 1).\n* **iconCreateFunction**: Function used to create the cluster icon. See [the default implementation](https://github.com/Leaflet/Leaflet.markercluster/blob/15ed12654acdc54a4521789c498e4603fe4bf781/src/MarkerClusterGroup.js#L542) or the [custom example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-custom.html).\n* **spiderfyShapePositions**: Function used to override spiderfy default shape positions. \n* **clusterPane**: Map pane where the cluster icons will be added. Defaults to L.Marker's default (currently 'markerPane'). [See the pane example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-pane.html).\n\n#### Chunked addLayers options\nOptions for the [addLayers](#bulk-adding-and-removing-markers) method. See [#357](https://github.com/Leaflet/Leaflet.markercluster/issues/357) for explanation on how the chunking works.\n* **chunkedLoading**: Boolean to split the addLayer**s** processing in to small intervals so that the page does not freeze.\n* **chunkInterval**: Time interval (in ms) during which addLayers works before pausing to let the rest of the page process. In particular, this prevents the page from freezing while adding a lot of markers. Defaults to 200ms.\n* **chunkDelay**: Time delay (in ms) between consecutive periods of processing for addLayers. Default to 50ms.\n* **chunkProgress**: Callback function that is called at the end of each chunkInterval. Typically used to implement a progress indicator, e.g. [code in RealWorld 50k](https://github.com/Leaflet/Leaflet.markercluster/blob/master/example/marker-clustering-realworld.50000.html#L33-L49). Defaults to null. Arguments:\n 1. Number of processed markers\n 2. Total number of markers being added\n 3. Elapsed time (in ms)\n\n## Events\nLeaflet events like `click`, `mouseover`, etc. are just related to _Markers_ in the cluster.\nTo receive events for clusters, listen to `'cluster' + ''`, ex: `clusterclick`, `clustermouseover`, `clustermouseout`.\n\nSet your callback up as follows to handle both cases:\n\n```javascript\nmarkers.on('click', function (a) {\n\tconsole.log('marker ' + a.layer);\n});\n\nmarkers.on('clusterclick', function (a) {\n\t// a.layer is actually a cluster\n\tconsole.log('cluster ' + a.layer.getAllChildMarkers().length);\n});\n```\n\n### Additional MarkerClusterGroup Events\n\n- **animationend**: Fires when marker clustering/unclustering animation has completed\n- **spiderfied**: Fires when overlapping markers get spiderified (Contains ```cluster``` and ```markers``` attributes)\n- **unspiderfied**: Fires when overlapping markers get unspiderified (Contains ```cluster``` and ```markers``` attributes)\n\n## Methods\n\n### Group methods\n\n#### Adding and removing Markers\n`addLayer`, `removeLayer` and `clearLayers` are supported and they should work for most uses.\n\n#### Bulk adding and removing Markers\n`addLayers` and `removeLayers` are bulk methods for adding and removing markers and should be favoured over the single versions when doing bulk addition/removal of markers. Each takes an array of markers. You can use [dedicated options](#chunked-addlayers-options) to fine-tune the behaviour of `addLayers`.\n\nThese methods extract non-group layer children from Layer Group types, even deeply nested. _However_, be noted that:\n- `chunkProgress` jumps backward when `addLayers` finds a group (since appending its children to the input array makes the total increase).\n- Groups are not actually added into the MarkerClusterGroup, only their non-group child layers. Therfore, `hasLayer` method will return `true` for non-group child layers, but `false` on any (possibly parent) Layer Group types.\n\nIf you are removing a lot of markers it will almost definitely be better to call `clearLayers` then call `addLayers` to add the markers you don't want to remove back in. See [#59](https://github.com/Leaflet/Leaflet.markercluster/issues/59#issuecomment-9320628) for details.\n\n#### Getting the visible parent of a marker\nIf you have a marker in your MarkerClusterGroup and you want to get the visible parent of it (Either itself or a cluster it is contained in that is currently visible on the map).\nThis will return null if the marker and its parent clusters are not visible currently (they are not near the visible viewpoint)\n```javascript\nvar visibleOne = markerClusterGroup.getVisibleParent(myMarker);\nconsole.log(visibleOne.getLatLng());\n```\n\n#### Refreshing the clusters icon\nIf you have [customized](#customising-the-clustered-markers) the clusters icon to use some data from the contained markers, and later that data changes, use this method to force a refresh of the cluster icons.\nYou can use the method:\n- without arguments to force all cluster icons in the Marker Cluster Group to be re-drawn.\n- with an array or a mapping of markers to force only their parent clusters to be re-drawn.\n- with an L.LayerGroup. The method will look for all markers in it. Make sure it contains only markers which are also within this Marker Cluster Group.\n- with a single marker.\n```javascript\nmarkers.refreshClusters();\nmarkers.refreshClusters([myMarker0, myMarker33]);\nmarkers.refreshClusters({id_0: myMarker0, id_any: myMarker33});\nmarkers.refreshClusters(myLayerGroup);\nmarkers.refreshClusters(myMarker);\n```\n\nThe plugin also adds a method on L.Marker to easily update the underlying icon options and refresh the icon.\nIf passing a second argument that evaluates to `true`, the method will also trigger a `refreshCluster` on the parent MarkerClusterGroup for that single marker.\n```javascript\n// Use as many times as required to update markers,\n// then call refreshClusters once finished.\nfor (i in markersSubArray) {\n\tmarkersSubArray[i].refreshIconOptions(newOptionsMappingArray[i]);\n}\nmarkers.refreshClusters(markersSubArray);\n\n// If updating only one marker, pass true to\n// refresh this marker's parent clusters right away.\nmyMarker.refreshIconOptions(optionsMap, true); \n```\n\n#### Other Group Methods\n* **hasLayer**(layer): Returns true if the given layer (marker) is in the MarkerClusterGroup.\n* **zoomToShowLayer**(layer, callback): Zooms to show the given marker (spiderfying if required), calls the callback when the marker is visible on the map.\n\n### Clusters methods\nThe following methods can be used with clusters (not the group). They are typically used for event handling.\n\n#### Getting the bounds of a cluster\nWhen you receive an event from a cluster you can query it for the bounds.\n```javascript\nmarkers.on('clusterclick', function (a) {\n\tvar latLngBounds = a.layer.getBounds();\n});\n```\n\nYou can also query for the bounding convex polygon.\nSee [example/marker-clustering-convexhull.html](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-convexhull.html) for a working example.\n```javascript\nmarkers.on('clusterclick', function (a) {\n\tmap.addLayer(L.polygon(a.layer.getConvexHull()));\n});\n```\n\n#### Zooming to the bounds of a cluster\nWhen you receive an event from a cluster you can zoom to its bounds in one easy step.\nIf all of the markers will appear at a higher zoom level, that zoom level is zoomed to instead.\n`zoomToBounds` takes an optional argument to pass [options to the resulting `fitBounds` call](http://leafletjs.com/reference.html#map-fitboundsoptions).\n\nSee [marker-clustering-zoomtobounds.html](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-zoomtobounds.html) for a working example.\n```javascript\nmarkers.on('clusterclick', function (a) {\n\ta.layer.zoomToBounds({padding: [20, 20]});\n});\n```\n\n#### Other clusters methods\n* **getChildCount**: Returns the total number of markers contained within that cluster.\n* **getAllChildMarkers(storage: array | undefined, ignoreDraggedMarker: boolean | undefined)**: Returns an array of all markers contained within this cluster (storage will be used if provided). If ignoreDraggedMarker is true and there is currently a marker dragged, the dragged marker will not be included in the array.\n* **spiderfy**: Spiderfies the child markers of this cluster\n* **unspiderfy**: Unspiderfies a cluster (opposite of spiderfy)\n\n## Handling LOTS of markers\nThe Clusterer can handle 10,000 or even 50,000 markers (in chrome). IE9 has some issues with 50,000.\n- [realworld 10,000 example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.10000.html)\n- [realworld 50,000 example](https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.50000.html)\n\nNote: these two examples use the `chunkedLoading` option set to true in order to avoid locking the browser for a long time.\n\n## License\n\nLeaflet.markercluster is free software, and may be redistributed under the MIT-LICENSE.\n\n[](https://travis-ci.org/Leaflet/Leaflet.markercluster)\n\n## Sub-plugins\nLeaflet.markercluster plugin is very popular and as such it generates high and\ndiverse expectations for increased functionalities.\n\nIf you are in that case, be sure to have a look first at the repository\n[issues](https://github.com/Leaflet/Leaflet.markercluster/issues) in case what\nyou are looking for would already be discussed, and some workarounds would be proposed.\n\nCheck also the below sub-plugins:\n\n| Plugin | Description | Maintainer |\n| :----- | :---------- | :--------- |\n| [Leaflet.FeatureGroup.SubGroup](https://github.com/ghybs/Leaflet.FeatureGroup.SubGroup) | Creates a Feature Group that adds its child layers into a parent group when added to a map (e.g. through L.Control.Layers). Typical usage is to dynamically add/remove groups of markers from Marker Cluster. | [ghybs](https://github.com/ghybs) |\n| [Leaflet.MarkerCluster.LayerSupport](https://github.com/ghybs/Leaflet.MarkerCluster.LayerSupport) | Brings compatibility with L.Control.Layers and other Leaflet plugins. I.e. everything that uses direct calls to map.addLayer and map.removeLayer. | [ghybs](https://github.com/ghybs) |\n| [Leaflet.MarkerCluster.Freezable](https://github.com/ghybs/Leaflet.MarkerCluster.Freezable) | Adds the ability to freeze clusters at a specified zoom. E.g. freezing at maxZoom + 1 makes as if clustering was programmatically disabled. | [ghybs](https://github.com/ghybs) |\n| [Leaflet.MarkerCluster.PlacementStrategies](https://github.com/adammertel/Leaflet.MarkerCluster.PlacementStrategies) | Implements new strategies to position clustered markers (eg: clock, concentric circles, ...). Recommended to use with circleMarkers. [Demo](https://adammertel.github.io/Leaflet.MarkerCluster.PlacementStrategies/demo/demo1.html) | [adammertel](https://github.com/adammertel) / [UNIVIE](http://carto.univie.ac.at/) |\n| [Leaflet.MarkerCluster.List](https://github.com/adammertel/Leaflet.MarkerCluster.List) | Displays child elements in a list. Suitable for mobile devices. [Demo](https://adammertel.github.io/Leaflet.MarkerCluster.List/demo/demo1.html) | [adammertel](https://github.com/adammertel) / [UNIVIE](http://carto.univie.ac.at/) |\n",
"name": "leaflet.markercluster@1.5.3",
"licenses": "MIT",
"repository": "https://github.com/Leaflet/Leaflet.markercluster"
},
{
"licenseText": "BSD 2-Clause License\r\n\r\nCopyright (c) 2010-2022, Vladimir Agafonkin\r\nCopyright (c) 2010-2011, CloudMade\r\nAll rights reserved.\r\n\r\nRedistribution and use in source and binary forms, with or without\r\nmodification, are permitted provided that the following conditions are met:\r\n\r\n1. Redistributions of source code must retain the above copyright notice, this\r\n list of conditions and the following disclaimer.\r\n\r\n2. Redistributions in binary form must reproduce the above copyright notice,\r\n this list of conditions and the following disclaimer in the documentation\r\n and/or other materials provided with the distribution.\r\n\r\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\"\r\nAND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE\r\nIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE\r\nDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE\r\nFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL\r\nDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR\r\nSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER\r\nCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,\r\nOR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE\r\nOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\r\n",
"name": "leaflet@1.9.3",
"licenses": "BSD-2-Clause",
"repository": "https://github.com/Leaflet/Leaflet"
},
{
"licenseText": "\n Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n\n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n 1. Definitions.\n\n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n\n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n\n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n\n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n\n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n\n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n\n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n\n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n\n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n\n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n\n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n\n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n\n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n\n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n\n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n\n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n\n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n\n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n\n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n\n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n\n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n\n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n\n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n\n END OF TERMS AND CONDITIONS\n\n APPENDIX: How to apply the Apache License to your work.\n\n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n\n Copyright [yyyy] [name of copyright owner]\n\n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n",
"name": "material-symbols@0.4.1",
"licenses": "Apache-2.0",
"repository": "https://github.com/marella/material-symbols"
},
{
"licenseText": "Copyright (c) JS Foundation and other contributors\n\nPermission is hereby granted, free of charge, to any person\nobtaining a copy of this software and associated documentation\nfiles (the \"Software\"), to deal in the Software without\nrestriction, including without limitation the rights to use,\ncopy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the\nSoftware is furnished to do so, subject to the following\nconditions:\n\nThe above copyright notice and this permission notice shall be\nincluded in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES\nOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND\nNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT\nHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,\nWHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR\nOTHER DEALINGS IN THE SOFTWARE.\n",
"name": "moment@2.29.4",
"licenses": "MIT",
"repository": "https://github.com/moment/moment",
"publisher": "Iskren Ivov Chernev",
"email": "iskren.chernev@gmail.com",
"url": "https://github.com/ichernev"
},
{
"licenseText": "The MIT License\n\nCopyright (c) 2018 David Fannin\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n",
"name": "ngx-logger@4.3.3",
"licenses": "MIT",
"repository": "https://github.com/dbfannin/ngx-logger",
"publisher": "David Fannin",
"email": "dbfannin.npm@gmail.com"
},
{
"licenseText": "MIT License\r\n\r\nCopyright (c) 2017-2021 Jean-Francois Cere\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\r\n",
"name": "ngx-markdown@13.1.0",
"licenses": "MIT",
"repository": "https://github.com/jfcere/ngx-markdown",
"publisher": "Jean-Francois Cere",
"email": "jfcere@hotmail.com"
},
{
"licenseText": "The MIT License (MIT)\n\nCopyright (c) 2013-2020 Uri Shaked and contributors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n",
"name": "ngx-moment@6.0.2",
"licenses": "MIT",
"repository": "https://github.com/urish/ngx-moment",
"publisher": "Uri Shaked"
},
{
"licenseText": "\n\n# opening_hours\n\n[![GitHub CI]](https://github.com/opening-hours/opening_hours.js/actions?query=workflow%3A%22Continuous+Integration%22)\n[][ohlib.github]\n[][ohlib.github]\n[][ohlib.npmjs]\n[][ohlib.npmjs]\n[][ohlib.npmjs]\n\n[github ci]: https://github.com/opening-hours/opening_hours.js/workflows/Continuous%20Integration/badge.svg\n\n\n\n\n## Summary\n\nThe [opening_hours][key:opening_hours] tag is used in [OpenStreetMap](https://openstreetmap.org) to describe time ranges when a facility (for example, a café) is open. This library exists to easily extract useful information (e.g. whether a facility is open at a specific time, next time it's going to open/close, or a readable set of working hours) from the [complex syntax][oh:specification].\n\nExamples of some complex opening_hours values:\n\n```text\nMo,Tu,Th,Fr 12:00-18:00; Sa,PH 12:00-17:00; Th[3],Th[-1] off\nMo-Fr 12:00-18:00; We off; Sa,PH 12:00-17:00; Th[3],Th[-1] off\n```\n\nA library which is open from 12:00 to 18:00 on workdays (Mo-Fr) except Wednesday, and from 12:00 to 17:00 on Saturday and public holidays. It also has breaks on the third and last Thursday of each month.\n\n```text\nopen; Tu-Su 08:30-09:00 off; Tu-Su,PH 14:00-14:30 off; Mo 08:00-13:00 off\n```\n\nAn around-the-clock shop with some breaks.\n\n\n\n## Table of Contents\n\n- [Evaluation tool](#evaluation-tool)\n- [Installation](#installation)\n - [For Developer](#for-developer)\n - [Web developer](#web-developer)\n - [NodeJS developer](#nodejs-developer)\n- [Versions](#versions)\n- [Synopsis](#synopsis)\n- [Library API](#library-api)\n - [Simple API](#simple-api)\n - [High-level API](#high-level-api)\n - [Iterator API](#iterator-api)\n- [Features](#features)\n - [Time ranges](#time-ranges)\n - [Points in time](#points-in-time)\n - [Weekday ranges](#weekday-ranges)\n - [Holidays](#holidays)\n - [Month ranges](#month-ranges)\n - [Monthday ranges](#monthday-ranges)\n - [Week ranges](#week-ranges)\n - [Year ranges](#year-ranges)\n - [States](#states)\n - [Comments](#comments)\n- [Testing](#testing)\n - [Regression testing](#regression-testing)\n - [Testing with real data](#testing-with-real-data)\n - [Large scale](#large-scale)\n - [Small scale](#small-scale)\n - [Test it yourself (the geeky way)](#test-it-yourself-the-geeky-way)\n- [Performance](#performance)\n- [Used by other projects](#used-by-other-projects)\n- [Projects that previously used the library](#projects-that-previously-used-the-library)\n - [YoHours](#yohours)\n- [Bindings and ports](#bindings-and-ports)\n- [Other implementations](#other-implementations)\n- [Related links](#related-links)\n- [ToDo](#todo)\n- [How to contribute](#how-to-contribute)\n - [Translating the evaluation tool and the map](#translating-the-evaluation-tool-and-the-map)\n - [Translating error messages and warnings](#translating-error-messages-and-warnings)\n - [Holiday Data](#holiday-data)\n - [Core code](#core-code)\n - [Commit hooks](#commit-hooks)\n - [Documentation](#documentation)\n- [Authors](#authors)\n- [Contributors](#contributors)\n- [Credits](#credits)\n- [Stats](#stats)\n- [License](#license)\n\n\n\n## Evaluation tool\n\nPlease have a look at the [evaluation tool] which can give you an impression of how this library can be used and what it is capable of.\n\nA mirror is set up at \n\n## Installation\n\n### For Developer\n\nJust clone the repository:\n\n```sh\ngit clone --recursive https://github.com/opening-hours/opening_hours.js.git\n```\n\nand install the required dependencies:\n\n```sh\nnpm install\npip install -r requirements.txt\n```\n\nand build the library:\n\n```sh\nnpm run build\n```\n\nSee the [Testing](#testing) section for details around writing and running tests\n\n### Web developer\n\nIf you are a web developer and want to use this library you can do so by including the current version from here:\n\n\n\nTo get started checkout the [simple_index.html](/examples/simple_index.html) file.\n\n### NodeJS developer\n\nInstall using npm/yarn.\n\n```sh\nnpm install opening_hours\n```\n\nor\n\n```sh\nyarn add opening_hours\n```\n\n## Versions\n\nThe version number consists of a major release, minor release and patch level (separated by a dot).\n\nFor version 2.2.0 and all later, [Semantic Versioning](http://semver.org/spec/v2.0.0.html) is used:\n\n- The major release is only increased if the release breaks backward compatibility.\n- The minor release is increased if new features are added.\n- The patch level is increased to bundle a bunch of commits (minor changes like bug fixes and improvements) into a new tested version.\n\nCheck [releases on GitHub] for a list of the releases and their Changelog.\n\n## Synopsis\n\n```js\nconst opening_hours = require(\"opening_hours\");\nvar oh = new opening_hours(\"We 12:00-14:00\");\n\nvar from = new Date(\"01 Jan 2012\");\nvar to = new Date(\"01 Feb 2012\");\n\n// high-level API\n{\n var intervals = oh.getOpenIntervals(from, to);\n for (var i in intervals)\n console.log(\n \"We are \" +\n (intervals[i][2] ? \"maybe \" : \"\") +\n \"open from \" +\n (intervals[i][3] ? '(\"' + intervals[i][3] + '\") ' : \"\") +\n intervals[i][0] +\n \" till \" +\n intervals[i][1] +\n \".\"\n );\n\n var duration_hours = oh.getOpenDuration(from, to).map(function (x) {\n return x / 1000 / 60 / 60;\n });\n if (duration_hours[0])\n console.log(\n \"For the given range, we are open for \" + duration_hours[0] + \" hours\"\n );\n if (duration_hours[1])\n console.log(\n \"For the given range, we are maybe open for \" +\n duration_hours[1] +\n \" hours\"\n );\n}\n\n// helper function\nfunction getReadableState(startString, endString, oh, past) {\n if (past === true) past = \"d\";\n else past = \"\";\n\n var output = \"\";\n if (oh.getUnknown()) {\n output +=\n \" maybe open\" +\n (oh.getComment()\n ? ' but that depends on: \"' + oh.getComment() + '\"'\n : \"\");\n } else {\n output +=\n \" \" +\n (oh.getState() ? \"open\" : \"close\" + past) +\n (oh.getComment() ? ', comment \"' + oh.getComment() + '\"' : \"\");\n }\n return startString + output + endString + \".\";\n}\n\n// simple API\n{\n var state = oh.getState(); // we use current date\n var unknown = oh.getUnknown();\n var comment = oh.getComment();\n var nextchange = oh.getNextChange();\n\n console.log(getReadableState(\"We're\", \"\", oh, true));\n\n if (typeof nextchange === \"undefined\")\n console.log(\"And we will never \" + (state ? \"close\" : \"open\"));\n else\n console.log(\n \"And we will \" +\n (oh.getUnknown(nextchange) ? \"maybe \" : \"\") +\n (state ? \"close\" : \"open\") +\n \" on \" +\n nextchange\n );\n}\n\n// iterator API\n{\n var iterator = oh.getIterator(from);\n\n console.log(getReadableState(\"Initially, we're\", \"\", iterator, true));\n\n while (iterator.advance(to)) {\n console.log(\n getReadableState(\"Then we\", \" at \" + iterator.getDate(), iterator)\n );\n }\n\n console.log(getReadableState(\"And till the end we're\", \"\", iterator, true));\n}\n```\n\n## Library API\n\n- `var oh = new opening_hours('We 12:00-14:00', nominatim_object, mode);`\n\n - `value (mandatory, type: string)`: Constructs opening_hours object, given the opening_hours tag value. Throws an error string if the expression is malformed or unsupported.\n\n - `nominatim_object (optional, type: object or null)`: Used in order to calculate the correct times for holidays and variable times (e.g. sunrise, dusk, see under [Time ranges][ohlib.time-ranges]).\n\n The nominatim-object should contain the fields `{lat, lon, address: {country_code, state}}`. The location (`lat` and `lon`) is used to calculate the correct values for sunrise and sunset.\n\n The country code and the state is needed to calculate the correct public holidays (PH) and school holidays (SH).\n\n Based on the coordinates or the OSM id of the facility, the other parameters can be queried using [reverse geocoding with Nominatim][nominatim].\n The JSON obtained from this online service can be passed in as the second argument of the constructor.\n The data returned by Nominatim should be in the local language (the language of the country for which the opening hours apply). If not, *accept-language* can be used as parameter in the request URL.\n To get started, see [this example query](https://nominatim.openstreetmap.org/reverse?format=json&lat=49.5487429714954&lon=9.81602098644987&zoom=5&addressdetails=1) or [have a look in the API-reference](https://nominatim.org/release-docs/develop/api/Overview/)\n\n The `nominatim_object` can also be `null` in which case a default location will be used.\n This can be used if you don’t care about correct opening hours for more complex opening_hours values.\n\n - `optional_conf_param (optional, either of type number or object)`:\n\n If this parameter is of the type number then it is interpreted as 'mode' (see below). Alternatively it can be an object with any of the following keys:\n\n - `mode (type: (integer) number, default: 0)`: In OSM, the syntax originally designed to describe opening hours, is now used to describe a few other things as well. Some of those other tags work with points in time instead of time ranges. To support this the mode can be specified. \\_Note that it is recommended to use the tag_key parameter instead, which automatically sets the appropriate mode.\\_If there is no mode specified, opening_hours.js will only operate with time ranges and will throw an error when the value contains points in times.\n\n - 0: time ranges (opening_hours, lit, …) default\n - 1: points in time\n - 2: both (time ranges and points in time, used by collection_times, service_times, …)\n\n - `tag_key (type: string, default: undefined)`: The name of the key (Tag key). For example 'opening_hours' or 'lit'. Please always specify this parameter. If you do, the mode will be derived from the 'tag_key' parameter. Default is undefined e.g. no default value.\n\n - `map_value (type: boolean, default: false)`: Map certain values to different (valid) oh values. For example for the lit tag the value 'yes' is valid but not for opening_hours.js. If this parameter 'yes' is mapped to `sunset-sunrise open \"specified as yes: At night (unknown time schedule or daylight detection)\"`.\n\n - `warnings_severity (type: number, default: 4)`: Can be one of the following numbers. The severity levels (including the codes) match the syslog specification. The default is level 4 to not break backwards compatibility. Lower levels e.g. 5 include higher levels e.g. 4.\n\n ```text\n 4: warning\n 5: notice\n 6: info\n 7: debug\n ```\n\n - `locale (type: string, default: i18next.language || 'en')`: Defines the locale for errors and warnings.\n\n - additional_rule_separator (type boolean, default true)`: Allows to disable the \"additional_rule_separator not used after time wrapping midnight\" check giving rise to the warning \"This rule overwrites parts of the previous rule. This happens because normal rules apply to the whole day and overwrite any definition made by previous rules. You can make this rule an additional rule by using a \",\" instead of the normal \";\" to separate the rules. Note that the overwriting can also be desirable in which case you can ignore this warning.\"\n\n- `var warnings = oh.getWarnings();`\n\n Get warnings which appeared during parsing as human readable string array with one element per violation. Almost all warnings can be auto-corrected and are probably interpreted as intended by the mapper. However, this is not a granite of course.\n\n This function performs some additional testing and can thus also theoretically throw an error like all other functions which parse the time.\n\n- `var prettified = oh.prettifyValue(argument_hash);`\n\n Return a prettified version of the opening_hours value. The value is generated by putting the tokens back together to a string.\n\n The function accepts an optional hash.\n\n The key 'conf' can hold another hash with configuration options. One example:\n\n ```js\n {\n rule_sep_string: '\\n',\n print_semicolon: false\n }\n ```\n\n Look in the source code if you need more.\n\n If the key 'rule_index' is a number then only the corresponding rule will be prettified.\n\n If the key 'get_internals' is true then an object containing internal stuff will be returned instead. The format of this internal object may change in minor release.\n\n- `var every_week_is_same = oh.isWeekStable();`\n\n Checks whether open intervals are same for every week. Useful for giving a user hint whether time table may change for another week.\n\n- `var is_equal_to = oh.isEqualTo(new opening_hours('We 12:00-16:00'), start_date);`\n\n Check if this opening_hours object has the same meaning as the given\n opening_hours object (evaluates to the same state for every given time).\n\n The optional parameter `start_date` (Date object) specifies the start date at which the comparison will begin.\n\n `is_equal_to` is a list:\n\n 1. Boolean which is true if both opening_hours objects have the same\n meaning, otherwise false.\n\n 2. Object hash containing more information when the given objects differ in meaning. Example:\n\n ```js\n {\n \"matching_rule\": 1,\n \"matching_rule_other\": 0,\n \"deviation_for_time\": {\n \"1445637600000\": [\n \"getState\",\n \"getUnknown\",\n \"getComment\",\n ],\n },\n }\n ```\n\n### Simple API\n\nThis API is useful for one-shot checks, but for iteration over intervals you should use the more efficient [iterator API][ohlib.iterator-api].\n\n- `var is_open = oh.getState(date);`\n\n Checks whether the facility is open at the given *date*. You may omit *date* to use current date.\n\n- `var unknown = oh.getUnknown(date);`\n\n Checks whether the opening state is conditional or unknown at the given *date*. You may omit *date* to use current date.\n Conditions can be expressed in comments.\n If unknown is true then is_open will be false since it is not sure if it is open.\n\n- `var state_string = oh.getStateString(date, past);`\n\n Return state string at given *date*. Either 'open', 'unknown' or 'closed?'. You may omit *date* to use current date.\n\n If the boolean parameter `past` is true you will get 'closed' else you will get 'close'.\n\n- `var comment = oh.getComment(date);`\n\n Returns the comment (if one is specified) for the facility at the given *date*. You may omit *date* to use current date.\n Comments can be specified for any state.\n\n If no comment is specified this function will return undefined.\n\n- `var next_change = oh.getNextChange(date, limit);`\n\n Returns date of next state change. You may omit *date* to use current date.\n\n Returns undefined if the next change cannot be found. This may happen if the state won't ever change (e.g. `24/7`) or if search goes beyond *limit* (which is *date* + ~5 years if omitted).\n\n- `var rule_index = oh.getMatchingRule(date);`\n\n Returns the internal rule number of the matching rule. You may omit *date* to use current date.\n A opening_hours string can consist of multiple rules from which one of them is used to evaluate the state for a given point in time. If no rule applies, the state will be closed and this function returns undefined.\n\n To prettify this rule, you can specify `rule_index` as parameter for `oh.prettifyValue` like this:\n\n ```js\n var matching_rule = oh.prettifyValue({ rule_index: rule_index });\n ```\n\n### High-level API\n\nHere and below, unless noted otherwise, all arguments are expected to be and all output will be in the form of Date objects.\n\n- `var intervals = oh.getOpenIntervals(from, to);`\n\n Returns array of open intervals in a given range, in a form of\n\n ```JavaScript\n [ [ from1, to1, unknown1, comment1 ], [ from2, to2, unknown2, comment2 ] ]\n ```\n\n Intervals are cropped with the input range.\n\n- `var duration = oh.getOpenDuration(from, to);`\n\n Returns an array with two durations for a given date range, in milliseconds. The first element is the duration for which the facility is open and the second is the duration for which the facility is maybe open (unknown is used).\n\n### Iterator API\n\n- `var iterator = oh.getIterator(date);`\n\n Constructs an iterator which can go through open/close points, starting at *date*. You may omit *date* to use current date.\n\n- `var current_date = iterator.getDate();`\n\n Returns current iterator position.\n\n- `iterator.setDate(date);`\n\n Set iterator position to date.\n\n- `var is_open = iterator.getState();`\n\n Returns whether the facility is open at the current iterator position.\n\n- `var unknown = iterator.getUnknown();`\n\n Checks whether the opening state is conditional or unknown at the current iterator position.\n\n- `var state_string = iterator.getStateString(past);`\n\n Return state string. Either 'open', 'unknown' or 'closed?'.\n\n If the boolean parameter `past` is true you will get 'closed' else you will get 'close'.\n\n- `var comment = iterator.getComment();`\n\n Returns the comment (if one is specified) for the facility at the current iterator position in time.\n\n If no comment is specified this function will return undefined.\n\n- `var matching_rule = iterator.getMatchingRule();`\n\n Returns the index of the matching rule starting with zero.\n\n- `var had_advanced = iterator.advance(limit);`\n\n Advances an iterator to the next position, but not further than *limit* (which is current position + ~5 years if omitted and is used to prevent infinite loop on non-periodic opening_hours, e.g. `24/7`), returns whether the iterator was moved.\n\n For instance, returns false if the iterator would go beyond *limit* or if there's no next position (`24/7` case).\n\n## Features\n\nAlmost everything from opening_hours definition is supported, as well as some extensions (indicated as **EXT** below).\n\n**WARN** indicates that the syntax element is evaluated correctly, but there is a better way to express this. A warning will be shown.\n\n- See the [formal specification][oh:specification] as of version `0.6.0`.\n\n- Opening hours consist of multiple rules separated by semicolon (`Mo 10:00-20:00; Tu 12:00-18:00`) or by other separators as follows.\n\n- Supports [fallback rules][oh:specification:fallback rule] (`We-Fr 10:00-24:00 open \"it is open\" || \"please call\"`).\n\n Note that only the rule which starts with `||` is a fallback rule. Other rules which might follow are considered as normal rules.\n\n- Supports [additional rules][oh:specification:additional rule] or cooperative values (`Mo-Fr 08:00-12:00, We 14:00-18:00`). A additional rule is treated exactly the same as a normal rule, except that a additional rule does not overwrite the day for which it applies. Note that a additional rule does not use any data from previous or from following rules.\n\n A rule does only count as additional rule if the previous rule ends with a time range (`12:00-14:00, We 16:00-18:00`, but does not continue with a time range of course), a comment (`12:00-14:00 \"call us\", We 16:00-18:00`) or the keywords 'open', 'unknown' or 'closed' (`12:00-14:00 unknown, We 16:00-18:00`)\n\n- Rule may use `off` keyword to indicate that the facility is closed at that time (`Mo-Fr 10:00-20:00; 12:00-14:00 off`). `closed` can be used instead if you like. They mean exactly the same.\n\n- Rule consists of multiple date (`Mo-Fr`, `Jan-Feb`, `week 2-10`, `Jan 10-Feb 10`) and time (`12:00-16:00`, `12:00-14:00,16:00-18:00`) conditions\n\n- If a rule's date condition overlap with previous rule, it overrides (as opposed to extends) the previous rule. E.g. `Mo-Fr 10:00-16:00; We 12:00-18:00` means that on Wednesday the facility is open from 12:00 till 18:00, not from 10:00 to 18:00.\n\n This also applies for time ranges spanning midnight. This is the only way to be consistent. Example: `22:00-02:00; Th 12:00-14:00`. By not overriding specifically for midnight ranges, we could get either `22:00-02:00; Th 00:00-02:00,12:00-14:00,22:00-02:00` or `22:00-02:00; Th 00:00-02:00,12:00-14:00` and deciding which interpretation was really intended cannot always be guessed.\n\n- Date ranges (calendar ranges) can be separated from the time range by a colon (`Jan 10-Feb 10: 07:30-12:00`) but this is not required. This was implemented to also parse the syntax proposed by [Netzwolf][oh:spec:separator_for_readability].\n\n### Time ranges\n\n- Supports sets of time ranges (`10:00-12:00,14:00-16:00`)\n\n - **WARN:** Accept `10-12,14-16` as abbreviation for the previous example. Please don’t use this as this is not very explicit.\n - Correctly supports ranges wrapping over midnight (`10:00-26:00`, `10:00-02:00`)\n\n- Supports 24/7 keyword (`24/7`, which means always open. Use [state keywords][ohlib.states] to express always closed.)\n\n - **WARN:** 24/7 is handled as a synonym for `00:00-24:00`, so `Mo-Fr 24/7` (though not really correct, because of that you should avoid it or replace it with \"open\". A warning will be given if you use it anyway for that purpose) will be handled correctly\n\n *The use of 24/7 as synonym is never needed and should be avoided in cases where it does not mean 24/7.* In cases where a facility is really open 24 hours 7 days a week thats where this value is for.\n\n- **WARN:** Supports omitting time range (`Mo-Fr; Tu off`)\n\n *A warning will be given as this is not very explicit. See [issue 49](https://github.com/opening-hours/opening_hours.js/issues/49).*\n\n- **WARN:** Supports space as time interval separator, i.e. `Mo 12:00-14:00,16:00-20:00` and `Mo 12:00-14:00 16:00-20:00` are the same thing\n- **WARN:** Supports dot as time separator (`12.00-16.00`)\n- Complete support for dawn/sunrise/sunset/dusk (variable times) keywords (`10:00-sunset`, `dawn-dusk`). To calculate the correct values, the latitude and longitude are required which are included in the JSON returned by [Nominatim] \\(see in the [Library API][ohlib.library-api] how to provide it\\). The calculation is done by [suncalc].\n\n If the coordinates are missing, constant times will be used (dawn: '05:30', sunrise: '06:00', sunset: '18:00', dusk: '18:30').\n\n If the end time (second time in time range) is near the sunrise (for instance `sunrise-08:00`) than it can happen that the sunrise would actually be after 08:00 which would normally be interpreted as as time spanning midnight. But with variable times, this only partly applies. The rule here is that if the end time is lesser than the constant time (or the actual time) for the variable time in the start time (in that example sunrise: '06:00') then it is interpreted as the end time spanning over midnight. So this would be a valid time range spanning midnight: `sunrise-05:59`.\n\n A second thing to notice is that if the variable time becomes greater than the end time and the end time is greater than the constant time than this time range will be ignored (e.g `sunrise-08:00` becomes `08:03-08:00` for one day, it is ignored for this day).\n\n- Support calculation with variable times (e.g. `sunrise-(sunset-00:30)`: meaning that the time range ends 30 minutes before sunset; `(sunrise+01:02)-(sunset-00:30)`).\n\n- Supports open end (`10:00+`). It is interpreted as state unknown and the comment \"Specified as open end. Closing time was guessed.\" if there is no comment specified.\n\n If a facility is open for a fix time followed by open end the shortcut `14:00-17:00+` can be used (see also [proposal page](https://wiki.openstreetmap.org/wiki/Proposed_features/opening_hours_open_end_fixed_time_extension)).\n\n Open end applies until the end of the day if the opening time is before 17:00. If the opening time is between 17:00 and 21:59 the open end time ends 10 hours after the opening. And if the opening time is after 22:00 (including 22:00) the closing time will be interpreted as 8 hours after the opening time.\n\n- `07:00+,12:00-16:00`: If an open end time is used in a way that the first time range includes the second one (`07:00+` is interpreted as `07:00-24:00` and thus includes the complete `12:00-16:00` time selector), the second time selector cuts of the part which would follow after 16:00.\n\n### Points in time\n\n- In mode 1 or 2, points in time are evaluated. Example: `Mo-Fr 12:00,15:00,18:00; Su (sunrise+01:00)`. Currently a point in time is interpreted as an interval of one minute. It was the easiest thing to implement and has some advantages. See [here](https://github.com/AMDmi3/opening_hours.js/issues/12) for discussion.\n- To express regular points in time, like each hour, a abbreviation can be used to express the previous example `Mo-Fr 12:00-18:00/03:00` which means from 12:00 to 18:00 every three hours.\n\n### Weekday ranges\n\n- Supports set of weekdays and weekday ranges (`Mo-We,Fr`)\n- Supports weekdays which wrap to the next week (`Fr-Mo`)\n- Supports constrained weekdays (`Th[1,2-3]`, `Fr[-1]`)\n- Supports calculations based on constrained weekdays (`Sa[-1],Sa[-1] +1 day` e.g. last weekend in the month, this also works if Sunday is in the next month)\n\n### Holidays\n\n- Supports public holidays (`open; PH off`, `PH 12:00-13:00`).\n\n - Countries with PH definition:\n\n - [Australia][ph-au]\n - [Austria][ph-at] ([footnotes][ph-at] are ignored)\n - [Belgium][ph-be] (See [issue #115](https://github.com/opening-hours/opening_hours.js/issues/115) for details)\n - [Brazil][ph-br]\n - [Canada][ph-ca]\n - [Czech Republic][ph-cz]\n - [Denmark][ph-dk]\n - [England and Wales][ph-gb]\n - [France][ph-fr]\n - [Germany][ph-de] ([footnotes][ph-de] are ignored)\n - [Hungary][ph-hu]\n - [Ireland][ph-ie]\n - [Italy][ph-it] (Without the Saint Patron day, see [comment](https://github.com/opening-hours/opening_hours.js/pull/74#issuecomment-76194891))\n - [Ivory Coast][ph-ci] (Without the four islamic holidays because they can not be calculated and depend on subjective ad-hoc definition)\n - [Netherlands][ph-ne]\n - [New Zealand][ph-nz] (Provincial holiday is not handled. See [PR #333](https://github.com/opening-hours/opening_hours.js/pull/333) for details.)\n - [Poland][ph-nl]\n - [Romania][ph-ro]\n - [Russian][ph-ru]\n - [Slovenian][ph-si]\n - [Sweden][ph-se]\n - [Switzerland][ph-ch]\n - [Ukraine][ph-ua]\n - [United states][ph-us] (Some special cases are [currently not handled](https://github.com/opening-hours/opening_hours.js/issues/69#issuecomment-74103181))\n - [Vietnam][ph-vn] (Some public holidays cannot currently be calulated by the library and are missing. See https://github.com/opening-hours/opening_hours.js/pull/388)\n\n - **EXT:** Supports limited calculations based on public holidays (e.g. `Sa,PH -1 day open`). The only two possibilities are currently +1 and -1. All other cases are not handled. This seems to be enough because the only thing which is really used is -1.\n\n- Support for school holidays (`SH 10:00-14:00`).\n\n - Countries with SH definition:\n\n - Germany, see [hc]\n - Austria\n - Romania\n - Hungary\n\n- There can be two cases which need to be separated (this applies for PH and SH):\n\n 1. `Mo-Fr,PH`: The facility is open Mo-Fr and PH. If PH is a Sunday for example the facility is also open. This is the default case.\n 2. **EXT:** `PH Mo-Fr`: The facility is only open if a PH falls on Mo-Fr. For example if a PH is on the weekday Wednesday then the facility will be open, if PH is Saturday it will be closed.\n\n- If there is no comment specified by the rule, the name of the holiday is used as comment.\n\n- To evaluate the correct holidays, the country code and the state (could be omitted but this will probably result in less correctness) are required which are included in the JSON returned by [Nominatim] \\(see in the [Library API][ohlib.library-api] how to provide it\\).\n\n- If your country or state is missing or wrong you can [add it][ohlib.contribute.holidays]. Please note that issues for missing or wrong holidays cannot be handled. There are just to many countries for them to be handled by one spare time maintainer. See also [issue #300](https://github.com/opening-hours/opening_hours.js/issues/300).\n\n### Month ranges\n\n- Supports set of months and month ranges (`Jan,Mar-Apr`)\n- Supports months which wrap to the next year (`Dec-Jan`)\n\n### Monthday ranges\n\n- Supports monthday ranges across multiple months (`Jan 01-Feb 03 10:00-20:00`)\n- Supports monthday ranges within single month (`Jan 01-26 10:00-20:00`), with periods as well `Jan 01-29/7 10:00-20:00`, period equals 1 should be avoided)\n- Supports monthday ranges with years (`2013 Dec 31-2014 Jan 02 10:00-20:00`, `2012 Jan 23-31 10:00-24:00`)\n- Supports monthday ranges based on constrained weekdays (`Jan Su[1]-Feb 03 10:00-20:00`)\n- Supports calculation based on constrained weekdays in monthday range (`Jan Su[1] +1 day-Feb 03 10:00-20:00`)\n- Supports movable events like easter (`easter - Apr 20: open \"Around easter\"`) Note that if easter would be after the 20th of April for one year, this will be interpreted as spanning into the next year currently.\n- Supports calculations based on movable events (`2012 easter - 2 days - 2012 easter + 2 days: open \"Around easter\"`)\n- Supports multiple monthday ranges separated by a comma (`Jan 23-31/3,Feb 1-12,Mar 1`)\n\n### Week ranges\n\n- [The ISO 8601 definition for week 01 is the week with the year's first Thursday in it.](https://en.wikipedia.org/wiki/ISO_week_date#First_week)\n- Supports week ranges (`week 04-07 10:00-20:00`)\n- Supports periodic weeks (`week 2-53/2 10:00-20:00`)\n- Supports multiple week ranges (`week 1,3-5,7-30/2 10:00-20:00`)\n\n### Year ranges\n\n- **EXT:** Supports year ranges (`2013,2015,2050-2053,2055/2,2020-2029/3 10:00-20:00`)\n\n- **EXT:** Supports periodic year (either limited by range or unlimited starting with given year) (`2020-2029/3,2055/2 10:00-20:00`)\n\n There is one exception. It is not necessary to use a year range with a period of one (`2055-2066/1 10:00-20:00`) because this means the same as just the year range without the period (`2055-2066 10:00-20:00`) and should be expressed like this …\n\n The _oh.getWarnings()_ function will give you a warning if you use this anyway.\n\n- **EXT:** Supports way to say that a facility is open (or closed) from a specified year without limit in the future (`2055+ 10:00-20:00`)\n\n### States\n\n- A facility can be in two main states for a given point in time: `open` (true) or `closed` (false).\n\n - But since the state can also depend on other information (e.g. weather depending, call us) than just the time, a third state (called `unknown`) can be expressed (`Mo unknown; Th-Fr 09:00-18:00 open`)\n\n In that case the main state is false and unknown is true for Monday.\n\n- instead of `closed` `off` will also work\n\n### Comments\n\n- Supports (additional) comments (`Mo unknown \"on appointment\"; Th-Fr 09:00-18:00 open \"female only\"; Su closed \"really\"`)\n\n - The string which is delimited by double-quotes can contain any character (except a double-quote sign)\n - unknown can be omitted (just a comment (without [state][ohlib.states]) will also result in unknown)\n - value can also be just a double-quoted string (`\"on appointment\"`) which will result in unknown for any given time.\n\n## Testing\n\nThis project has become so complex that development without extensive testing would be madness.\n\n### Regression testing\n\nA node.js based test framework is bundled. You can run it with `node test/test.js` or with `make check-full`. Note that the number of lines of the test framework almost match up with the number of lines of the actual implementation :)\n\nIncluded in the `test` directory are the log outputs of the previous testing runs. By comparing to these logs and assuming that the checkedd-in logs are always passing, it allows the developer to validate if the number of passed tests have changed since the last feature implementation.\n\nThe current results of this test are also tracked in the repository and can be viewed [here](/test.en.log). Note that this file uses [ANSI escape code](https://en.wikipedia.org/wiki/ANSI_escape_code) which can be interpreted by cat in the terminal. `make check` compares the test output with the output from the last commit and shows you a diff.\n\n### Testing with real data\n\n#### Large scale\n\nTo see how this library performances in the real OpenStreetMap world you can run `make osm-tag-data-check` or `node scripts/real_test.js` (data needs to be exported first) to try to process every value which uses the opening_hours syntax from [taginfo] with this library.\n\nCurrently (Mai 2015) this library can parse 97 % (383990/396167) of all opening_hours values in OSM. If identical values appear multiple times then each value counts.\nThis test is automated by now. Have a look at the [opening_hours-statistics][].\n\n#### Small scale\n\nA python script to search with regular expressions over OSM opening_hours style tags is bundled. You can run it with `make run-regex_search` or `./scripts/regex_search.py` which will search on the opening_hours tag. To search over different tags either use `make run-regex_search \"SEARCH=$tagname\"` (this also makes sure that the tag you would like to search on will be downloaded if necessary) or run `./scripts/regex_search.py $path_to_downloaded_taginfo_json_file`.\n\nThis script not only shows you if the found value can be processed with this library or not, it also indicates using different colors if the facility is currently open (open: green, unknown: magenta, closed: blue).\n\nIt also offers filter options (e.g. only errors) and additional things like a link to [taginfo].\n\nHint: If you want to do quality assurance on tags like opening_hours you can also use this script and enter a regex for values you would like to check and correct (if you have no particular case just enter a dot which matches any character which results in every value being selected). Now you see how many values match your search pattern. As you do QA you probably only want to see values which can not be evaluated. To do this enter the filter \"failed\".\nTo improve the speed of fixing errors, a [feature](https://github.com/opening-hours/opening_hours.js/issues/29) was added to load those failed values in JOSM. To enable this, append \" josm\" to the input line. So you will have something like \"failed josm\" as argument. Now you can hit enter and go through the values.\n\n[taginfo]: https://taginfo.openstreetmap.org/\n\n### Test it yourself (the geeky way)\n\nYou want to try some opening_hours yourself? Just run `make run-interactive_testing` or `node ./scripts/interactive_testing.js` which will open an primitive interpreter. Just write your opening_hours value and hit enter and you will see if it can be processed (with current state) or not (with error message). The answer is JSON encoded.\n\nTesting is much easier by now. Have a look at the [evaluation tool][ohlib.evaluation-tool]. The reason why this peace of code was written is to have an interface which can be accessed from other programming languages. It is used by the python module [pyopening_hours].\n\n## Performance\n\nSimple node.js based benchmark is bundled. You can run it with `node ./scripts/benchmark.js` or with `make benchmark`.\n\nThe library allows ~9k/sec constructor calls and ~9k/sec openIntervals() calls with one week period on author's Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz running NodeJS 7.7.1, Linux 4.4.38-11 virtualized under Xen/Qubes OS). This may further improve in the future.\n\n## Used by other projects\n\nThis library is known to the used by the following projects:\n\n| Project | Additional Information |\n| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| [osm24.eu](https://github.com/dotevo/osm24) |\n| [OpenBeerMap](https://openbeermap.github.io) | [issue for integration](https://github.com/OpenBeerMap/OpenBeerMap.github.io/issues/25) |\n| [opening_hours_map] |\n| [ulm-opening-hours](https://github.com/cmichi/ulm-opening-hours) |\n| [YoHours][] | A simple editor for OpenStreetMap opening hours, [GitHub](https://github.com/PanierAvide/panieravide.github.io/tree/master/yohours) |\n| [opening_hours_server.js] | A little server answering query‘s for opening_hours and check if they can be evaluated. |\n| [opening_hours-statistics] | Visualization of the data quality and growth over time in OSM. |\n| [www.openstreetmap.hu](http://www.openstreetmap.hu/) | old version of this library, see also |\n| [osmopeninghours][] | JavaScript library which provides a more abstract, specialized API and Italian localization. It returns a JavaScript object for a given time interval (see [example.json](https://github.com/digitalxmobile-dev/osmopeninghours/blob/master/example/example.json)). |\n| [ComplexAlarm](https://github.com/ypid/ComplexAlarm) | Java/Android. Using the JS implementation through [js-evaluator-for-android](https://github.com/evgenyneu/js-evaluator-for-android). |\n| [MapComplete](https://github.com/pietervdvn/MapComplete) | An OpenStreetMap-editor which aims to be really simple to use by offering multiple themes |\n\nIf you use this library please let me know.\n\n## Projects that previously used the library\n\n| Project | Additional Information |\n| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| [JOSM](https://josm.openstreetmap.de/) | [ticket for integration in 13.11](https://josm.openstreetmap.de/ticket/9157), [ticket for removal in 20.03](https://josm.openstreetmap.de/ticket/18140) |\n\n### YoHours\n\nYoHours currently only checks with this lib if the opening_hours value can be evaluated at all and links to the [evaluation tool][ohlib.evaluation-tool] if yes. There might be more integration with YoHours and opening_hours.js in the future. See \n\n[opening_hours_map]: https://github.com/opening-hours/opening_hours_map\n[pyopening_hours]: https://github.com/ypid/pyopening_hours\n[opening_hours_server.js]: https://github.com/ypid/opening_hours_server.js\n[opening_hours-statistics]: https://github.com/ypid/opening_hours-statistics\n[yohours]: http://github.pavie.info/yohours/\n[osmopeninghours]: https://github.com/digitalxmobile-dev/osmopeninghours\n\n## Bindings and ports\n\n- Python: (using the JS implementation through Python subprocess and JSON passing to a Node.JS process executing the JS implementation, access to the [simple API](https://github.com/opening-hours/opening_hours.js#simple-api))\n- Java/Nashorn: (using the JS implementation through [Nashorn](https://openjdk.java.net/projects/nashorn/), Status: Nashorn provides access to all features of the JS implementation)\n- Java/Android: (using the JS implementation through [js-evaluator-for-android](https://github.com/evgenyneu/js-evaluator-for-android), Status: Library runs on Android, Return code/Result passing from JS to Java not yet clear/tested)\n\n## Other implementations\n\n- Java: (Implementation using [JavaCC](https://de.wikipedia.org/wiki/JavaCC) as Lexer/Parser compiler generator, Status: Basic language features implemented)\n- PHP: (reimplementation, Status: Basic language features implemented)\n- C: Implementation in C.\n- JavaScript: In the words of the author \"It only supports the human readable parts and not this complete crazy overengineered specification.\" Only covers a very small subset of the spec and API, which is a design goal. There is no clear definition/spec what \"simple\" or \"crazy\" means (seems subjective and might change over time, ref: [open end syntax listed as TODO in the code](https://github.com/ubahnverleih/simple-opening-hours/blob/a81c9f2b260114be049e335b6a751977f9425919/src/simple-opening-hours.ts#L32)). Also refer to [issue 143](https://github.com/opening-hours/opening_hours.js/issues/143#issuecomment-259721731).\n- Ruby: \n\n## Related links\n\n- [fossgis project page on the OSM wiki][fossgis-project]\n\n## ToDo\n\nList of missing features which can currently not be expressing in any other way without much pain.\nPlease share your opinion on the [talk page](https://wiki.openstreetmap.org/wiki/Talk:Key:opening_hours) (or the discussion page of the proposal if that does exist) if you have any idea how to express this (better).\n\n- Select single (or more, comma separated) (school|public) holidays. [Proposed syntax](https://wiki.openstreetmap.org/wiki/Proposed_features/opening_hours_holiday_select): `SH(Sommerferien)`\n- Depending on moon position like `\"low tide only\"`. Suncalc lib does support moon position. Syntax needed.\n- If weekday is PH than the facility will be open weekday-1 this week. Syntax something like: `We if (We +1 day == PH) else Th` ???\n\nList of features which can make writing easier:\n\n- `May-Aug: (Mo-Th 9:00-20:00; Fr 11:00-22:00; Sa-Su 11:00-20:00)`\n\n- Last day of the month.\n\n ```text\n Jan 31,Mar 01 -1 day,Mar 31,Apr 30,May 31,Jun 30,Jul 31,Aug 31,Sep 30,Oct 31,Nov 30,Dec 31 open\n ```\n\n Better syntax needed? This example is valid even if the evaluation tool does not agree. It simily does not yet implement this.\n\n Ref and source: \n\n## How to contribute\n\nYou can contribute in the usual manner as known from git (and GitHub). Just fork, change and make a pull request.\n\n### Translating the evaluation tool and the map\n\nThis project uses for translation.\n\nTranslations can be made in the file [js/i18n-resources.js][ohlib.js/i18n-resources.js]. Just copy the whole English block, change the language code to the one you are adding and make your translation. You can open the [index.html](/index.html) to see the result of your work. ~~To complete your localization add the translated language name to the other languages~~ (you don’t have to do this anymore. Importing that form somewhere, WIP, see gen_word_error_correction.js). Week and month names are translated by the browser using the `Date.toLocaleString` function.\n\nNote that this resource file does also provide the localization for the [opening_hours_map]. This can also be tested by cloning the project and linking your modified opening_hours.js working copy to the opening_hours.js directory (after renaming it) inside the opening_hours_map project. Or just follow the installation instructions from the [opening_hours_map].\n\n### Translating error messages and warnings\n\nTranslations for error messages and warnings for the opening_hours.js library can be made in the file [locales/core.js][ohlib.js/locales/core.js]. You are encouraged to test your translations. Checkout the [Makefile][ohlib.makefile] and the [test framework][ohlib.test.js] for how this can be done.\n\n### Holiday Data\n\nPlease do not open issues for missing holidays. It is obvious that there are more missing holidays then holidays which are defined in this library. Instead consider if you can add your missing holidays and send me a pull request or patch. If you are hitting a problem because some holidays depend on variable days or something like this, consider opening a unfinished PR so that the more complicated things can be discussed there.\n\nHolidays can be added to the file [index.js][ohlib.opening_hours.js]. Have a look at the current definitions for [other holidays][ohlib.holidays].\n\nPlease refer to the [holiday documentation][ohlib.docs.holiday] for more details about the data format.\n\nPlease consider adding a test (with a time range of one year for example) to see if everything works as expected and to ensure that it will stay that way.\nSee under [testing][ohlib.testing].\n\nIn case your holiday definition does only change the `holiday_definitions` variable (and not core code) it is also ok to test the definition using the `scripts/PH_SH_exporter.js` script. In that case writing a test is not required but still appreciated. Example: `./scripts/PH_SH_exporter.js --verbose --from=2016 --to=2016 --public-holidays --country dk --state dk /tmp/dk_holidays.txt`\n\n### Core code\n\nBe sure to add one or more tests if you add new features or enhance error tolerance or the like.\nSee under [testing][ohlib.testing].\n\n#### Commit hooks\n\nNote that there is a git pre-commit hook used to run and compare the test framework before each commit. Hooks are written as shell scripts using [husky](https://github.com/typicode/husky) and should be installed to git automatically when running `npm install`. If this does not happen, you can manually run `npm run postinstall`.\n\n#### Documentation\n\nAll functions are documented, which should help contributers to get started.\n\nThe documentation looks like this:\n\n```js\n/* List parser for constrained weekdays in month range {{{\n * e.g. Su[-1] which selects the last Sunday of the month.\n *\n * :param tokens: List of token objects.\n * :param at: Position where to start.\n * :returns: Array:\n * 0. Constrained weekday number.\n * 1. Position at which the token does not belong to the list any more (after ']' token).\n */\nfunction getConstrainedWeekday(tokens, at) {}\n```\n\nThe opening brackets `{{{` (and the corresponding closing onces) are used to fold the source code. See [Vim folds](http://vim.wikia.com/wiki/Folding).\n\n## Authors\n\n| Autor | Contact | Note |\n| --------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| [Dmitry Marakasov](https://github.com/AMDmi3) | | Initial coding and design and all basic features like time ranges, week ranges, month ranges and week ranges. |\n| [Robin Schneider](https://me.ypid.de/) | | Maintainer (since September 2013). Added support for years, holidays, unknown, comments, open end, fallback/additional rules (and more), wrote getWarnings, prettifyValue, translated demo page to English and German and extended it to enter values yourself (now called [evaluation tool][ohlib.evaluation-tool]). |\n\n## Contributors\n\nRefer to the [Changelog](https://github.com/opening-hours/opening_hours.js/blob/master/CHANGELOG.rst)\n\n## Credits\n\n- [Netzwolf](http://www.netzwolf.info/) (He developed the first and very feature complete JS implementation for opening_hours (time_domain.js, [mirror](https://openingh.ypid.de/netzwolf_mirror/)). His implementation did not create selector code to go through time as this library does (which is a more advanced design). time_domain.js has been withdrawn in favor of opening_hours.js but a few parts where reused (mainly the error tolerance and the online evaluation for the [evaluation tool][ohlib.evaluation-tool]). It was also very useful as prove and motivation that all those complex things used in the [opening_hours syntax][oh:specification] are possible to evaluate with software :) )\n- Also thanks to FOSSGIS for hosting a public instance of this service. See the [wiki][fossgis-project].\n- The [favicon.png](/img/favicon.png) is based on the file ic_action_add_alarm.png from the [Android Design Icons](https://developer.android.com/downloads/design/Android_Design_Icons_20131106.zip) which is licensed under [Creative Commons Attribution 2.5](https://creativecommons.org/licenses/by/2.5/). It represents a clock next to the most common opening_hours value (by far) which is `24/7` and a check mark.\n\n## Stats\n\n- [Open HUB](https://www.openhub.net/p/opening_hours)\n\n## License\n\nAs of version 3.4, opening_hours.js is licensed under the [GNU Lesser General Public License v3.0]() only.\n\nNote that the original work from Dmitry Marakasov is published under the BSD 2-clause \"Simplified\" (BSD-2-Clause) license which is included in this repository under the commit hash [b2e11df02c76338a3a32ec0d4e964330d48bdd2d](https://github.com/opening-hours/opening_hours.js/tree/b2e11df02c76338a3a32ec0d4e964330d48bdd2d).\n\n\n\n[nominatim]: https://wiki.openstreetmap.org/wiki/Nominatim#Reverse_Geocoding_.2F_Address_lookup\n[suncalc]: https://github.com/mourner/suncalc\n[fossgis-project]: https://wiki.openstreetmap.org/wiki/FOSSGIS/Server/Projects/opening_hours.js\n[issue-report]: /../../issues\n[releases on github]: /../../releases\n[key:opening_hours]: https://wiki.openstreetmap.org/wiki/Key:opening_hours\n[oh:specification]: https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification\n[oh:specification:fallback rule]: https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#fallback_rule_separator\n[oh:specification:additional rule]: https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#additional_rule_separator\n[oh:spec:any_rule_separator]: https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#any_rule_separator\n[oh:spec:separator_for_readability]: https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#separator_for_readability\n\n\n\n[ohlib.iterator-api]: #iterator-api\n[ohlib.time-ranges]: #time-ranges\n[ohlib.states]: #states\n[ohlib.holidays]: #holidays\n[ohlib.contribute.holidays]: /src/holidays/\n[ohlib.evaluation-tool]: #evaluation-tool\n[ohlib.library-api]: #library-api\n[ohlib.testing]: #testing\n[ohlib.docs.holiday]: /holidays/README.md\n[ohlib.js/locales/core.js]: /src/locales/core.js\n[ohlib.opening_hours.js]: /index.js\n[ohlib.test.js]: /test.js\n[ohlib.makefile]: /Makefile\n[ohlib.js/i18n-resources.js]: /site/js/i18n-resources.js\n[ohlib.npmjs]: https://www.npmjs.org/package/opening_hours\n[ohlib.github]: https://github.com/opening-hours/opening_hours.js\n[hc]: https://gitlab.com/ypid/hc\n[evaluation tool]: https://openingh.openstreetmap.de/evaluation_tool/\n[schulferien.org]: http://www.schulferien.org/iCal/\n[ph-at]: https://de.wikipedia.org/wiki/Feiertage_in_%C3%96sterreich\n[ph-au]: https://en.wikipedia.org/wiki/Public_holidays_in_Australia\n[ph-be]: https://de.wikipedia.org/wiki/Feiertage_in_Belgien\n[ph-br]: https://pt.wikipedia.org/wiki/Feriados_no_Brasil\n[ph-ca]: https://en.wikipedia.org/wiki/Public_holidays_in_Canada\n[ph-ch]: https://www.bj.admin.ch/dam/bj/de/data/publiservice/service/zivilprozessrecht/kant-feiertage.pdf.download.pdf/kant-feiertage.pdf\n[ph-ci]: https://fr.wikipedia.org/wiki/Jour_f%C3%A9ri%C3%A9#_C%C3%B4te_d%27Ivoire\n[ph-cz]: https://en.wikipedia.org/wiki/Public_holidays_in_the_Czech_Republic\n[ph-de]: https://de.wikipedia.org/wiki/Feiertage_in_Deutschland\n[ph-dk]: https://en.wikipedia.org/wiki/Public_holidays_in_Denmark\n[ph-fr]: https://fr.wikipedia.org/wiki/F%EAtes_et_jours_f%E9ri%E9s_en_France\n[ph-gb]: https://www.gov.uk/bank-holidays#england-and-wales\n[ph-hu]: https://en.wikipedia.org/wiki/Public_holidays_in_Hungary\n[ph-ie]: https://en.wikipedia.org/wiki/Public_holidays_in_the_Republic_of_Ireland\n[ph-it]: http://www.governo.it/Presidenza/ufficio_cerimoniale/cerimoniale/giornate.html\n[ph-ne]: https://nl.wikipedia.org/wiki/Feestdagen_in_Nederland\n[ph-nl]: https://pl.wikipedia.org/wiki/Dni_wolne_od_pracy_w_Polsce\n[ph-nz]: https://en.wikipedia.org/wiki/Public_holidays_in_New_Zealand\n[ph-ro]: https://en.wikipedia.org/wiki/Public_holidays_in_Romania#Official_non-working_holidays\n[ph-ru]: https://ru.wikipedia.org/wiki/%D0%9F%D1%80%D0%B0%D0%B7%D0%B4%D0%BD%D0%B8%D0%BA%D0%B8_%D0%A0%D0%BE%D1%81%D1%81%D0%B8%D0%B8\n[ph-se]: https://en.wikipedia.org/wiki/Public_holidays_in_Sweden\n[ph-si]: http://www.vlada.si/o_sloveniji/politicni_sistem/prazniki/\n[ph-ua]: https://uk.wikipedia.org/wiki/%D0%A1%D0%B2%D1%8F%D1%82%D0%B0_%D1%82%D0%B0_%D0%BF%D0%B0%D0%BC%27%D1%8F%D1%82%D0%BD%D1%96_%D0%B4%D0%BD%D1%96_%D0%B2_%D0%A3%D0%BA%D1%80%D0%B0%D1%97%D0%BD%D1%96\n[ph-us]: https://en.wikipedia.org/wiki/Public_holidays_in_the_United_States\n[ph-vn]: https://vi.wikipedia.org/wiki/C%C3%A1c_ng%C3%A0y_l%E1%BB%85_%E1%BB%9F_Vi%E1%BB%87t_Nam\n\n\n",
"name": "opening_hours@3.8.0",
"licenses": "LGPL-3.0-only",
"repository": "https://github.com/opening-hours/opening_hours.js",
"publisher": "Dmitry Marakasov",
"email": "amdmi3@amdmi3.ru"
},
{
"licenseText": " Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n\n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n 1. Definitions.\n\n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n\n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n\n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n\n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n\n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n\n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n\n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n\n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n\n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n\n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n\n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n\n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n\n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n\n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n\n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n\n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n\n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n\n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n\n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n\n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n\n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n\n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n\n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n\n END OF TERMS AND CONDITIONS\n\n APPENDIX: How to apply the Apache License to your work.\n\n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n\n Copyright (c) 2015-2018 Google, Inc., Netflix, Inc., Microsoft Corp. and contributors\n\n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n \n",
"name": "rxjs@7.8.0",
"licenses": "Apache-2.0",
"repository": "https://github.com/reactivex/rxjs",
"publisher": "Ben Lesh",
"email": "ben@benlesh.com"
},
{
"licenseText": "The MIT License (MIT)\n\nCopyright (c) 2019 Vladimir Kharlampidi\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of\nthis software and associated documentation files (the \"Software\"), to deal in\nthe Software without restriction, including without limitation the rights to\nuse, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of\nthe Software, and to permit persons to whom the Software is furnished to do so,\nsubject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS\nFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR\nCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER\nIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN\nCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n",
"name": "swiper@8.4.5",
"licenses": "MIT",
"repository": "https://github.com/nolimits4web/Swiper",
"publisher": "Vladimir Kharlampidi"
},
{
"licenseText": "Copyright (c) Microsoft Corporation.\r\n\r\nPermission to use, copy, modify, and/or distribute this software for any\r\npurpose with or without fee is hereby granted.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH\r\nREGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY\r\nAND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,\r\nINDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM\r\nLOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR\r\nOTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR\r\nPERFORMANCE OF THIS SOFTWARE.",
"name": "tslib@2.4.1",
"licenses": "0BSD",
"repository": "https://github.com/Microsoft/tslib",
"publisher": "Microsoft Corp."
},
{
"licenseText": "The MIT License\n\nCopyright (c) 2010-2022 Google LLC. https://angular.io/license\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n",
"name": "zone.js@0.12.0",
"licenses": "MIT",
"repository": "https://github.com/angular/angular",
"publisher": "Brian Ford"
}
]