lokalise-upgrade-migration

Featured

Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection. Use when upgrading Lokalise SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade lokalise", "lokalise migration", "lokalise breaking changes", "update lokalise SDK", "analyze lokalise version".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Lokalise Upgrade Migration ## Current State !`npm list @lokalise/node-api 2>/dev/null | grep lokalise || echo 'SDK not installed'` !`lokalise2 --version 2>/dev/null || echo 'CLI not installed'` !`node --version 2>/dev/null || echo 'Node.js not available'` !`cat package.json 2>/dev/null | grep -E '"type"|"module"' || echo 'No package.json type field'` ## Overview Upgrade the `@lokalise/node-api` SDK between major versions with full breaking change detection, automated code transformation, and verification. The most significant migration is v8 (CommonJS) to v9+ (ESM-only), which requires changes to imports, module configuration, and potentially your build pipeline. ## Prerequisites - Existing project using `@lokalise/node-api` (any version 6.x through 9.x) - Node.js 18+ for SDK v9 (Node.js 14+ for v8 and below) - Git repository with clean working tree (for safe rollback) - Test suite that exercises Lokalise API calls ## Instructions ### Step 1: Assess Current Version and Target ```bash set -euo pipefail echo "=== Current SDK Version ===" CURRENT=$(npm list @lokalise/node-api --json 2>/dev/null | node -e " const d = JSON.parse(require('fs').readFileSync(0,'utf8')); const v = d.dependencies?.['@lokalise/node-api']?.version || 'not found'; console.log(v); ") echo "Installed: ${CURRENT}" echo -e "\n=== Latest Available ===" LATEST=$(npm view @lokalise/node-api version) echo "Latest: ${LATEST}" echo -e "\n=== All Major Versions ===" npm view @lokalise/node-api vers...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

lokalise-migration-deep-dive

Execute major migration to Lokalise from other TMS platforms with data migration strategies. Use when migrating to Lokalise from competitors, performing data imports, or re-platforming existing translation management to Lokalise. Trigger with phrases like "migrate to lokalise", "lokalise migration", "switch to lokalise", "lokalise import", "lokalise replatform".

2,266 Updated today
jeremylongshore
AI & Automation Featured

lokalise-install-auth

Install and configure Lokalise SDK/CLI authentication. Use when setting up a new Lokalise integration, configuring API tokens, or initializing Lokalise in your project. Trigger with phrases like "install lokalise", "setup lokalise", "lokalise auth", "configure lokalise API token".

2,266 Updated today
jeremylongshore
AI & Automation Featured

linear-upgrade-migration

Upgrade Linear SDK versions and handle breaking changes safely. Use when updating to a new SDK version, handling deprecations, or migrating between API versions. Trigger: "upgrade linear SDK", "linear SDK migration", "update linear", "linear breaking changes", "linear deprecation".

2,266 Updated today
jeremylongshore
AI & Automation Featured

elevenlabs-upgrade-migration

Upgrade ElevenLabs SDK versions and migrate between API model generations. Use when upgrading the elevenlabs-js or elevenlabs Python SDK, migrating from v1 to v2 models, or handling deprecations. Trigger: "upgrade elevenlabs", "elevenlabs migration", "elevenlabs breaking changes", "update elevenlabs SDK", "migrate elevenlabs model", "eleven_v3 migration".

2,266 Updated today
jeremylongshore
AI & Automation Featured

klaviyo-upgrade-migration

Upgrade Klaviyo SDK versions and migrate between API revisions. Use when upgrading the klaviyo-api package, migrating from v1/v2 legacy APIs to the current REST API, or handling breaking changes between revisions. Trigger with phrases like "upgrade klaviyo", "klaviyo migration", "klaviyo breaking changes", "update klaviyo SDK", "klaviyo API revision".

2,266 Updated today
jeremylongshore