@roxyapi/ui 0.40.0 → 0.41.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (98) hide show
  1. package/components-catalog.json +149 -149
  2. package/dist/cdn/components/choghadiya-grid.js +1 -1
  3. package/dist/cdn/components/choghadiya-grid.js.map +2 -2
  4. package/dist/cdn/components/endpoint-form.js +1 -1
  5. package/dist/cdn/components/endpoint-form.js.map +1 -1
  6. package/dist/cdn/components/hora-table.js +1 -1
  7. package/dist/cdn/components/hora-table.js.map +2 -2
  8. package/dist/cdn/components/horoscope-card.js +3 -3
  9. package/dist/cdn/components/horoscope-card.js.map +3 -3
  10. package/dist/cdn/components/vedic-daily.js +4 -4
  11. package/dist/cdn/components/vedic-daily.js.map +3 -3
  12. package/dist/cdn/locales/de.js +1 -1
  13. package/dist/cdn/locales/de.js.map +2 -2
  14. package/dist/cdn/locales/es.js +1 -1
  15. package/dist/cdn/locales/es.js.map +2 -2
  16. package/dist/cdn/locales/fr.js +1 -1
  17. package/dist/cdn/locales/fr.js.map +2 -2
  18. package/dist/cdn/locales/hi.js +1 -1
  19. package/dist/cdn/locales/hi.js.map +2 -2
  20. package/dist/cdn/locales/pt.js +1 -1
  21. package/dist/cdn/locales/pt.js.map +2 -2
  22. package/dist/cdn/locales/ru.js +1 -1
  23. package/dist/cdn/locales/ru.js.map +2 -2
  24. package/dist/cdn/locales/tr.js +1 -1
  25. package/dist/cdn/locales/tr.js.map +2 -2
  26. package/dist/cdn/roxy-ui.js +40 -40
  27. package/dist/cdn/roxy-ui.js.map +3 -3
  28. package/dist/components/choghadiya-grid.js +1 -1
  29. package/dist/components/choghadiya-grid.js.map +2 -2
  30. package/dist/components/endpoint-form.js +1 -1
  31. package/dist/components/endpoint-form.js.map +1 -1
  32. package/dist/components/hora-table.js +1 -1
  33. package/dist/components/hora-table.js.map +2 -2
  34. package/dist/components/horoscope-card.d.ts +10 -0
  35. package/dist/components/horoscope-card.d.ts.map +1 -1
  36. package/dist/components/horoscope-card.js +1 -1
  37. package/dist/components/horoscope-card.js.map +3 -3
  38. package/dist/components/vedic-daily.d.ts +7 -0
  39. package/dist/components/vedic-daily.d.ts.map +1 -1
  40. package/dist/components/vedic-daily.js +1 -1
  41. package/dist/components/vedic-daily.js.map +3 -3
  42. package/dist/i18n/chrome-strings.d.ts +1 -1
  43. package/dist/i18n/chrome-strings.d.ts.map +1 -1
  44. package/dist/index.cjs +38 -38
  45. package/dist/index.cjs.map +3 -3
  46. package/dist/index.js +41 -41
  47. package/dist/index.js.map +3 -3
  48. package/dist/locales/de.d.ts.map +1 -1
  49. package/dist/locales/de.js +1 -1
  50. package/dist/locales/de.js.map +2 -2
  51. package/dist/locales/es.d.ts.map +1 -1
  52. package/dist/locales/es.js +1 -1
  53. package/dist/locales/es.js.map +2 -2
  54. package/dist/locales/fr.d.ts.map +1 -1
  55. package/dist/locales/fr.js +1 -1
  56. package/dist/locales/fr.js.map +2 -2
  57. package/dist/locales/hi.d.ts.map +1 -1
  58. package/dist/locales/hi.js +1 -1
  59. package/dist/locales/hi.js.map +2 -2
  60. package/dist/locales/pt.d.ts.map +1 -1
  61. package/dist/locales/pt.js +1 -1
  62. package/dist/locales/pt.js.map +2 -2
  63. package/dist/locales/ru.d.ts.map +1 -1
  64. package/dist/locales/ru.js +1 -1
  65. package/dist/locales/ru.js.map +2 -2
  66. package/dist/locales/tr.d.ts.map +1 -1
  67. package/dist/locales/tr.js +1 -1
  68. package/dist/locales/tr.js.map +2 -2
  69. package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
  70. package/dist/schemas/post--vedic-astrology-kp-rasi-changes.json +1 -1
  71. package/dist/schemas/post--vedic-astrology-kp-sublord-changes.json +1 -1
  72. package/dist/styles/themes/practitioner.css +5 -5
  73. package/dist/types/types.gen.d.ts +100 -170
  74. package/dist/types/types.gen.d.ts.map +1 -1
  75. package/dist/version.d.ts +1 -1
  76. package/package.json +1 -1
  77. package/src/components/choghadiya-grid.ts +1 -1
  78. package/src/components/hora-table.ts +1 -1
  79. package/src/components/horoscope-card.ts +79 -61
  80. package/src/components/vedic-daily.ts +65 -0
  81. package/src/i18n/chrome-strings.ts +18 -1
  82. package/src/locales/de.ts +6 -1
  83. package/src/locales/es.ts +7 -1
  84. package/src/locales/field-labels/de.ts +2 -0
  85. package/src/locales/field-labels/es.ts +2 -0
  86. package/src/locales/field-labels/fr.ts +2 -0
  87. package/src/locales/field-labels/hi.ts +2 -0
  88. package/src/locales/field-labels/pt.ts +2 -0
  89. package/src/locales/field-labels/ru.ts +2 -0
  90. package/src/locales/field-labels/tr.ts +2 -0
  91. package/src/locales/fr.ts +6 -1
  92. package/src/locales/hi.ts +7 -1
  93. package/src/locales/pt.ts +7 -1
  94. package/src/locales/ru.ts +6 -1
  95. package/src/locales/tr.ts +8 -1
  96. package/src/styles/themes/practitioner.css +5 -5
  97. package/src/types/types.gen.ts +100 -170
  98. package/src/version.ts +1 -1
@@ -1 +1 @@
1
- {"title":"Get current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri"},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general"}],"hasLang":true}
1
+ {"title":"Get current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri"},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean"},{"key":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-08-23T13:47:46"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Find KP rasi ingress times","fields":[{"key":"planet","name":"planet","kind":"text","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","example":"Sun"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"Start date for sign ingress search (YYYY-MM-DD format)","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"End date for sign ingress search (YYYY-MM-DD format)","example":"2025-12-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb"},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean"}],"hasLang":false}
1
+ {"title":"Find KP rasi ingress times","fields":[{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Sun"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-12-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb"},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean"}],"hasLang":false}
@@ -1 +1 @@
1
- {"title":"Find KP sublord changes","fields":[{"key":"planet","name":"planet","kind":"text","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","example":"Moon"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"Start date for sublord change search (YYYY-MM-DD format)","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"End date for sublord change search (YYYY-MM-DD format)","example":"2025-01-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb"},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean"}],"hasLang":false}
1
+ {"title":"Find KP sublord changes","fields":[{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Moon"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-01-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb"},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean"}],"hasLang":false}
@@ -27,7 +27,7 @@
27
27
  font-style: normal;
28
28
  font-weight: 400 600;
29
29
  font-display: swap;
30
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.40.0/dist/styles/fonts/fraunces/fraunces-latin.woff2")
30
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.41.0/dist/styles/fonts/fraunces/fraunces-latin.woff2")
31
31
  format("woff2");
32
32
  unicode-range:
33
33
  U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
@@ -38,7 +38,7 @@
38
38
  font-style: normal;
39
39
  font-weight: 400 600;
40
40
  font-display: swap;
41
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.40.0/dist/styles/fonts/fraunces/fraunces-latin-ext.woff2")
41
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.41.0/dist/styles/fonts/fraunces/fraunces-latin-ext.woff2")
42
42
  format("woff2");
43
43
  unicode-range:
44
44
  U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
@@ -49,7 +49,7 @@
49
49
  font-style: normal;
50
50
  font-weight: 400 600;
51
51
  font-display: swap;
52
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.40.0/dist/styles/fonts/jost/jost-latin.woff2")
52
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.41.0/dist/styles/fonts/jost/jost-latin.woff2")
53
53
  format("woff2");
54
54
  unicode-range:
55
55
  U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
@@ -60,7 +60,7 @@
60
60
  font-style: normal;
61
61
  font-weight: 400 600;
62
62
  font-display: swap;
63
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.40.0/dist/styles/fonts/jost/jost-latin-ext.woff2")
63
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.41.0/dist/styles/fonts/jost/jost-latin-ext.woff2")
64
64
  format("woff2");
65
65
  unicode-range:
66
66
  U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
@@ -71,7 +71,7 @@
71
71
  font-style: normal;
72
72
  font-weight: 400 600;
73
73
  font-display: swap;
74
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.40.0/dist/styles/fonts/jost/jost-cyrillic.woff2")
74
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.41.0/dist/styles/fonts/jost/jost-cyrillic.woff2")
75
75
  format("woff2");
76
76
  unicode-range: U+0301, U+0400-045F, U+0490-0491, U+04B0-04B1, U+2116;
77
77
  }