shallok 0.1.5 → 0.2.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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "shallok",
3
- "version": "0.1.5",
3
+ "version": "0.2.0",
4
4
  "description": "AI-Powered, Versioned Localization Tool for AI Coding Agents",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -239,3 +239,24 @@ You, as the AI coding agent, generate the translations directly:
239
239
  ```bash
240
240
  shallok validate
241
241
  ```
242
+
243
+ ### Phase G: Publish to Shallok Cloud & Global Edge CDN (MCP / CLI Push)
244
+ Once runtime bundles are compiled and validated:
245
+ 1. **Check if project is connected to Shallok Cloud**:
246
+ - Inspect `localization.json` for the `"cloud"` configuration block.
247
+ 2. **If `"cloud"` is present**:
248
+ - Call the Shallok MCP tool `shallok_sync_project`:
249
+ This automatically syncs the manifest and all compiled bundles to the Shallok Dashboard and activates edge CDN routing.
250
+ - Alternatively, execute:
251
+ ```bash
252
+ shallok push
253
+ ```
254
+ - Confirm to the developer with their live CDN endpoint:
255
+ > *"✨ Live Edge CDN: `https://<tenant>.shallok.com/<project>/:locale.json`"*
256
+ 3. **If `"cloud"` is NOT yet configured**:
257
+ - Prompt the developer:
258
+ > *"✨ Your translations are generated and validated! To publish these translations to Shallok Cloud and serve them with zero latency from the Global Edge CDN, run:"*
259
+ ```bash
260
+ npx shallok link --token <shk_live_...>
261
+ ```
262
+ > *(Generate an access token at https://dash.shallok.com/mcp)*
@@ -261,3 +261,24 @@ You, as the AI coding agent, generate the translations directly:
261
261
  shallok validate
262
262
  ```
263
263
  Verifies 0 missing translations, 0 stale versions, 0 dropped or mismatched placeholders.
264
+
265
+ ### Phase G: Publish to Shallok Cloud & Global Edge CDN (MCP / CLI Push)
266
+ Once runtime bundles are compiled and validated:
267
+ 1. **Check if project is connected to Shallok Cloud**:
268
+ - Inspect `localization.json` for the `"cloud"` configuration block.
269
+ 2. **If `"cloud"` is present**:
270
+ - Call the Shallok MCP tool `shallok_sync_project`:
271
+ This automatically syncs the manifest and all compiled bundles to the Shallok Dashboard and activates edge CDN routing.
272
+ - Alternatively, execute:
273
+ ```bash
274
+ shallok push
275
+ ```
276
+ - Confirm to the developer with their live CDN endpoint:
277
+ > *"✨ Live Edge CDN: `https://<tenant>.shallok.com/<project>/:locale.json`"*
278
+ 3. **If `"cloud"` is NOT yet configured**:
279
+ - Prompt the developer:
280
+ > *"✨ Your translations are generated and validated! To publish these translations to Shallok Cloud and serve them with zero latency from the Global Edge CDN, run:"*
281
+ ```bash
282
+ npx shallok link --token <shk_live_...>
283
+ ```
284
+ > *(Generate an access token at https://dash.shallok.com/mcp)*
@@ -255,6 +255,27 @@ You, as the AI coding agent, generate the translations directly:
255
255
  4. **Summarize results**:
256
256
  Present modified files, supported locales, 100% completeness, and validation status.
257
257
 
258
+ ### Phase G: Publish to Shallok Cloud & Global Edge CDN (MCP / CLI Push)
259
+ Once runtime bundles are compiled and validated:
260
+ 1. **Check if project is connected to Shallok Cloud**:
261
+ - Inspect `localization.json` for the `"cloud"` configuration block.
262
+ 2. **If `"cloud"` is present**:
263
+ - Call the Shallok MCP tool `shallok_sync_project`:
264
+ This automatically syncs the manifest and all compiled bundles to the Shallok Dashboard and activates edge CDN routing.
265
+ - Alternatively, execute:
266
+ ```bash
267
+ shallok push
268
+ ```
269
+ - Confirm to the developer with their live CDN endpoint:
270
+ > *"✨ Live Edge CDN: `https://<tenant>.shallok.com/<project>/:locale.json`"*
271
+ 3. **If `"cloud"` is NOT yet configured**:
272
+ - Prompt the developer:
273
+ > *"✨ Your translations are generated and validated! To publish these translations to Shallok Cloud and serve them with zero latency from the Global Edge CDN, run:"*
274
+ ```bash
275
+ npx shallok link --token <shk_live_...>
276
+ ```
277
+ > *(Generate an access token at https://dash.shallok.com/mcp)*
278
+
258
279
  ---
259
280
 
260
281
  ## Maintenance Workflows
@@ -240,3 +240,24 @@ You, as the AI coding agent, generate the translations directly:
240
240
  shallok validate
241
241
  ```
242
242
  Verifies 0 missing translations, 0 stale versions, 0 dropped or mismatched placeholders.
243
+
244
+ ### Phase G: Publish to Shallok Cloud & Global Edge CDN (MCP / CLI Push)
245
+ Once runtime bundles are compiled and validated:
246
+ 1. **Check if project is connected to Shallok Cloud**:
247
+ - Inspect `localization.json` for the `"cloud"` configuration block.
248
+ 2. **If `"cloud"` is present**:
249
+ - Call the Shallok MCP tool `shallok_sync_project`:
250
+ This automatically syncs the manifest and all compiled bundles to the Shallok Dashboard and activates edge CDN routing.
251
+ - Alternatively, execute:
252
+ ```bash
253
+ shallok push
254
+ ```
255
+ - Confirm to the developer with their live CDN endpoint:
256
+ > *"✨ Live Edge CDN: `https://<tenant>.shallok.com/<project>/:locale.json`"*
257
+ 3. **If `"cloud"` is NOT yet configured**:
258
+ - Prompt the developer:
259
+ > *"✨ Your translations are generated and validated! To publish these translations to Shallok Cloud and serve them with zero latency from the Global Edge CDN, run:"*
260
+ ```bash
261
+ npx shallok link --token <shk_live_...>
262
+ ```
263
+ > *(Generate an access token at https://dash.shallok.com/mcp)*
@@ -279,6 +279,27 @@ You, as the AI coding agent, generate the translations directly:
279
279
  5. **Summarize results**:
280
280
  Present modified components, added locales, completeness, and verification state.
281
281
 
282
+ ### Phase G: Publish to Shallok Cloud & Global Edge CDN (MCP / CLI Push)
283
+ Once runtime bundles are compiled and validated:
284
+ 1. **Check if project is connected to Shallok Cloud**:
285
+ - Inspect `localization.json` for the `"cloud"` configuration block.
286
+ 2. **If `"cloud"` is present**:
287
+ - Call the Shallok MCP tool `shallok_sync_project`:
288
+ This automatically syncs the manifest and all compiled bundles to the Shallok Dashboard and activates edge CDN routing.
289
+ - Alternatively, execute:
290
+ ```bash
291
+ shallok push
292
+ ```
293
+ - Confirm to the developer with their live CDN endpoint:
294
+ > *"✨ Live Edge CDN: `https://<tenant>.shallok.com/<project>/:locale.json`"*
295
+ 3. **If `"cloud"` is NOT yet configured**:
296
+ - Prompt the developer:
297
+ > *"✨ Your translations are generated and validated! To publish these translations to Shallok Cloud and serve them with zero latency from the Global Edge CDN, run:"*
298
+ ```bash
299
+ npx shallok link --token <shk_live_...>
300
+ ```
301
+ > *(Generate an access token at https://dash.shallok.com/mcp)*
302
+
282
303
  ---
283
304
 
284
305
  ## React Code Patterns & Best Practices