Knowledge base for updating @lenne.tech/nest-server. Use when discussing nest-server updates, upgrades, migrations, breaking changes, or version compatibility. Provides resources, migration guide patterns, and error solutions. For execution, use the nest-server-updater agent.
/plugin marketplace add lenneTech/claude-code/plugin install lt-dev@lenne-techThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides knowledge and resources for updating @lenne.tech/nest-server. For automated execution, use the nest-server-updater agent via /lt-dev:backend:update-nest-server.
| Element | Purpose |
|---|---|
Agent: nest-server-updater | Automated execution of updates |
Command: /lt-dev:backend:update-nest-server | User invocation |
Skill: generating-nest-servers | Code modifications after update |
Skill: npm-package-maintenance | Package optimization |
| Resource | URL | Purpose |
|---|---|---|
| nest-server | https://github.com/lenneTech/nest-server | Main package repository |
| Releases | https://github.com/lenneTech/nest-server/releases | Release notes, changelogs |
| Migration Guides | https://github.com/lenneTech/nest-server/tree/main/migration-guides | Version-specific migration instructions |
| Reference Project | https://github.com/lenneTech/nest-server-starter | Current compatible code & package versions |
# Package info
npm view @lenne.tech/nest-server
# Current installed version
npm list @lenne.tech/nest-server --depth=0
# All available versions
npm view @lenne.tech/nest-server versions --json
Migration guides in migration-guides/ follow these patterns:
| Pattern | Example | Scope |
|---|---|---|
X.Y.x-to-A.B.x.md | 11.6.x-to-11.7.x.md | Minor version step |
X.x-to-Y.x.md | 11.x-to-12.x.md | Major version jump |
X.Y.x-to-A.B.x.md | 11.6.x-to-12.0.x.md | Spanning multiple versions |
For an update from version CURRENT to TARGET:
List available guides:
gh api repos/lenneTech/nest-server/contents/migration-guides --jq '.[].name'
Select applicable guides:
| Condition | Guides to load |
|---|---|
| Same major, sequential minor | Each X.Y.x-to-X.Z.x.md in sequence |
| Major version jump | All minor guides + X.x-to-Y.x.md |
| Spanning guide exists | Include it (may consolidate steps) |
Load order (example 11.6.0 → 12.1.0):
1. 11.6.x-to-11.7.x.md
2. 11.7.x-to-11.8.x.md
3. ... (all minor steps to 11.x latest)
4. 11.x-to-12.x.md (major jump)
5. 12.0.x-to-12.1.x.md
6. 11.6.x-to-12.x.md (if exists - consolidated)
Fetch guide content:
gh api repos/lenneTech/nest-server/contents/migration-guides/11.6.x-to-11.7.x.md \
--jq '.content' | base64 -d
Or via URL:
https://raw.githubusercontent.com/lenneTech/nest-server/main/migration-guides/11.6.x-to-11.7.x.md
If migration-guides/ is empty or no matching guides exist for the version range:
Fallback Priority Order:
| Priority | Source | How to Use |
|---|---|---|
| 1 | Release Notes | Extract breaking changes from GitHub Releases |
| 2 | Reference Project | Compare nest-server-starter between version tags |
| 3 | CHANGELOG.md | Check nest-server repo for changelog entries |
Fallback Commands:
# Get all releases between versions
gh release list --repo lenneTech/nest-server --limit 50
# View specific release details
gh release view v11.7.0 --repo lenneTech/nest-server
# Compare reference project between versions
cd /tmp/nest-server-starter-ref
git log --oneline v11.6.0..v11.8.0
git diff v11.6.0..v11.8.0 -- package.json src/
When using fallback:
IMPORTANT: In @lenne.tech/nest-server, Major versions are reserved for NestJS Major versions. Therefore, Minor versions are treated like Major versions and may contain breaking changes.
11.6.0 → 11.6.5 - direct update OK11.6.0 → 11.8.0 becomes 11.6 → 11.7 → 11.811.6.0 → 12.2.0 becomes:
11.6 → 11.7 → ... → 11.latest (all minors)11.latest → 12.0 (major jump)12.0 → 12.1 → 12.2 (all minors)| Error | Cause | Solution |
|---|---|---|
Cannot find module '@lenne.tech/nest-server/...' | Import path changed | Check migration guide for new paths |
Type 'X' is not assignable to type 'Y' | API type changed | Update to new type signature per guide |
Property 'X' does not exist | API removed/renamed | Check migration guide for replacement |
| Error | Cause | Solution |
|---|---|---|
Decorator not found | Decorator moved | Import from new location |
Cannot read property of undefined | Initialization changed | Check startup sequence in reference project |
Module not found | Peer dependency missing | Compare package.json with reference project |
| Symptom | Cause | Solution |
|---|---|---|
| Timeout errors | Async behavior changed | Check test patterns in reference project |
| Auth failures | Auth mechanism updated | Review auth changes in migration guide |
| Validation errors | DTO changes | Update DTOs per migration guide |
The nest-server-starter serves as the source of truth:
package.json
src/config.env.ts
src/server/modules/
Git history
git log --oneline --all --grep="nest-server" | head -20
The nest-server-updater agent supports these modes:
| Mode | Flag | Behavior |
|---|---|---|
| Full | (default) | Complete update with all migrations |
| Dry-Run | --dry-run | Analysis only, no changes |
| Target Version | --target-version X.Y.Z | Update to specific version |
| Skip Packages | --skip-packages | Skip npm-package-maintainer optimization |
# Check current version
npm list @lenne.tech/nest-server --depth=0
# Check latest version
npm view @lenne.tech/nest-server version
# List migration guides
gh api repos/lenneTech/nest-server/contents/migration-guides --jq '.[].name'
IMPORTANT: The npm run update script requires a specific workflow:
First: Update the version in package.json to the desired target version
"@lenne.tech/nest-server": "^X.Y.Z"
Then: Run the update script
npm run update
What npm run update does:
@lenne.tech/nest-server at the version from package.json@lenne.tech/nest-server were updatedManual update (only if npm run update script is not available):
npm install @lenne.tech/nest-server@X.Y.Z --save-exact
npm install
Note: This skips the automatic dependency synchronization that npm run update provides.
After npm run update completes, run comprehensive package maintenance:
# Via command (recommended)
/lt-dev:maintenance:maintain
# Or via agent (Task tool with npm-package-maintainer in FULL MODE)
This ensures:
npm run build # Must pass
npm run lint # Must pass
npm test # Must pass (no skips)
npm audit # Should show no new vulnerabilities
| Scenario | Recommendation |
|---|---|
| Routine update to latest | Use agent: /lt-dev:backend:update-nest-server |
| Check what would change | Use agent with --dry-run |
| Update to specific version | Use agent with --target-version X.Y.Z |
| Complex issues during update | Use this skill's knowledge + manual fixes |
| Understanding breaking changes | Read this skill + migration guides |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.