@getmicdrop/venue-calendar 4.3.9 → 4.3.10

package/dist/{zh-CM2J1Py4.js → zh-D2ZAdq3T.js}

@@ -48,6 +48,13 @@ var e = {
 	cancel: "取消",
 	continue: "继续",
 	submit: "提交",
+	addOns: "附加项目",
+	addOnRedeemBar: "在吧台领取",
+	addOnRedeemHost: "请到接待处登记",
+	addOnRedeemMerch: "在周边商品台领取",
+	addOnCollectInPerson: "现场领取",
+	addOnNeedsTicket: "请先添加门票",
+	addOnPerTicketLimit: "每张门票最多 {count} 件",
 	subtotal: "小计",
 	serviceFees: "服务费",
 	taxes: "税费",
@@ -187,7 +194,13 @@ var e = {
 	queueWaitMinutes: "{n} 分钟",
 	queueKeepPageOpen: "请保持此页面打开，您的位置已为您保留",
 	queueAdmittedTitle: "轮到您了",
-	queueAdmittedBody: "轮到您了，现在可以购票"
+	queueAdmittedBody: "轮到您了，现在可以购票",
+	recommendationsHeading: "该场地的更多演出",
+	recommendationFromTonightsLineup: "来自今晚的阵容",
+	recommendationSimilarShow: "相似演出",
+	recommendationSameNight: "同一星期几",
+	recommendationYouMightLike: "你可能也喜欢",
+	recommendationFeatured: "精选"
 };
 //#endregion
 export { e as zh };

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@getmicdrop/venue-calendar",
   "_version_comment": "4.1.55 was the last PUBLISHED version, and the tree carried 36 commits npm's 4.1.55 does not have — including the gate-password security fix and four money fixes. A filename must never reuse a version npm has taken (jsDelivr/unpkg cache the FIRST bytes they see under `@4.1.55` forever, so republishing that number ships the old widget to every venue that pinned it). Bumped to 4.2.0 here, BEFORE anything is built for publish. `npm run release:preflight` refuses to proceed when this number already exists in the registry.",
-  "version": "4.3.9",
+  "version": "4.3.10",
   "description": "A customizable Svelte calendar component for displaying comedy events",
   "type": "module",
   "types": "./dist/types/index.d.ts",
@@ -154,7 +154,7 @@
   "_devDependencies_pin_comment": "Three EXACT pins in here are load-bearing and must not be re-caretted by a dependency bot. (1) `@getmicdrop/svelte-components` — the ES/UMD/IIFE builds do NOT externalize SC, so it is COMPILED INTO every shipped artifact. RESTORED TO AN EXACT PIN 2026-08-23, having drifted back to a caret at some point between 6.24.311 and 6.24.316 — exactly the re-caretting this note warns about, which is worth knowing recurs. Under a caretted range like `^6.24.311` the SC version a venue's browser executes is whatever the range floats to on the publish machine at publish time, which is not recorded anywhere and is not reproducible after the fact; the `overrides` block below cannot help (it only ever covered esbuild, and consumers ignore a dependency's overrides entirely). Pinned exact so the artifact and the manifest agree, and vite.config.lib.js stamps the resolved version into the bundle as __VC_SC_VERSION__ so a venue's devtools can answer 'which SC is this?'. (2) `svelte` — the compiler whose private internal/client calls the pre-compiled dist binds to. `^5.56.9` let the compiler move under a peer range that stayed still; see _peerDependencies_comment. (3) `@stripe/stripe-js` in dependencies — see its own note there.",
   "devDependencies": {
     "@eslint/js": "^10.0.1",
-    "@getmicdrop/svelte-components": "6.24.339",
+    "@getmicdrop/svelte-components": "6.24.340",
     "@playwright/test": "^1.60.0",
     "@size-limit/file": "^13.0.3",
     "@sveltejs/adapter-auto": "^7.0.1",