Agent skill

Tsed Migration

by tsedio in tsedio/tsed

Migrates an application to Ts.ED v8 from v7, with pointers for v6 and plain Express apps.

MITAuto-check passedTesting & QA

Install Tsed Migration

skills CLI
$ npx skills add tsedio/tsed --skill tsed-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tsedio/tsed tsed-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tsedio/tsed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/tsed/skills/tsed-migration .claude/skills/tsed-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tsed-migration
GitHub stars
3.1k
Token cost
~2.5k tokens
SKILL.md length
956 words
Files
4 (incl. references)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Migrates an application to Ts.ED v8 from v7, with pointers for v6 and plain Express apps.

  • Works in 8 steps: Assess → Prepare on v7: compiler and… → Prepare on v7: switch to ESM → …
  • Package.json has @tsed/ 6.x
  • SKILL.md covers 1. Assess, 2. Prepare on v7: compiler and…, 3. Prepare on v7: switch to ESM and 4. Verify on v7, plus 6 more sections
  • Calls npx, npm and node; reaches tsed.dev

What it does

Tsed Migration is an agent skill from tsedio/tsed. Migrates an application to Ts.ED v8 from v7, with pointers for v6 and plain Express apps. Covers the ESM switch (type module, NodeNext, .js extensions, @tsed/barrels), useDefineForClassFields false, removal of settings.prop proxy access, replacing @tsed/common imports, deprecated DI APIs (registerProvider, injector.getProvider, PlatformTest.inject) and Jest to Vitest. Use when package.json has @tsed/ 6.x or 7.x or @tsed/common, on ERRREQUIREESM, ERRMODULENOTFOUND, "has no exported member" from @tsed/common…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/common-symbols.md` and `references/deprecated-apis.md`).

It sits in Testing & QA, covering Unit testing. It works with Vitest, Jest and npm. The repository describes itself as: :triangularruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline… The licence is MIT.

When your agent uses it

  • Package.json has @tsed/ 6.x
  • On ERRREQUIREESM
  • ERRMODULENOTFOUND
  • Has no exported member from @tsed/common

Example prompts

  • “has no exported member”
  • “Use the tsed-migration skill to migrate an application to Ts.ED v8 from v7, with pointers for v6 and plain Express apps”
  • “/tsed-migration”

Requirements

  • Node.js

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Assess
  2. Prepare on v7: compiler and configuration access
  3. Prepare on v7: switch to ESM
  4. Verify on v7
  5. Bump to v8
  6. Remove @tsed/common
  7. Tests: Jest to Vitest
  8. Plain Express application

What it can do on your machine

Read from SKILL.md and the folder at commit cebcc11. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • npm
    • node
    • vitest

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • tsed.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tsed Migration loads about 2.5k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 956 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tsedio/tsed at commit cebcc11, republished under its MIT licence (© tsedio). 956 words, ~2,513 tokens.

Download SKILL.mdSave it as .claude/skills/tsed-migration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tsed-migration
description
Migrates an application to Ts.ED v8 from v7, with pointers for v6 and plain Express apps. Covers the ESM switch (type module, NodeNext, .js extensions, @tsed/barrels), useDefineForClassFields false, removal of settings.prop proxy access, replacing @tsed/common imports, deprecated DI APIs (registerProvider, injector.getProvider, PlatformTest.inject) and Jest to Vitest. Use when package.json has @tsed/* 6.x or 7.x or @tsed/common, on ERR_REQUIRE_ESM, ERR_MODULE_NOT_FOUND, "has no exported member" from @tsed/common, undefined injected properties, or a request to upgrade Ts.ED.

Migrate to Ts.ED v8

Migrate in small, verifiable steps. v7 already supports ESM, useDefineForClassFields: false and settings.get(), so do all preparation on v7, verify, and only then bump to v8.

References, loaded on demand:

Live guide: https://tsed.dev/introduction/migrate-from-v7.md and https://tsed.dev/introduction/what-is-news-v8.md.

1. Assess

  1. Read package.json: the @tsed/* major, the type field, the test runner, the dev runner (ts-node, ts-node-dev, tsx, SWC), barrelsby.
  2. Read tsconfig.json, .swcrc, vite.config.ts / vitest.config.ts, jest.config.*.
  3. Pick the path:
Starting pointPath
v7Sections 2 to 7
v6First reach the latest v7 with https://tsed.dev/introduction/migrate-from-v6.md, verify, then sections 2 to 7
v5 or olderDo not upgrade in place. Scaffold a v8 project with the tsed-cli skill and port code feature by feature
Plain Express appSection 8
  1. Confirm Node.js >= 20.11.0 (>= 22 when the Ts.ED CLI v7 is used).
  2. Require a clean git tree and a passing test suite before starting. Commit after each section.

Do not bump @tsed/* to 8.x before sections 2 to 4 pass on v7.

2. Prepare on v7: compiler and configuration access

  1. Update every @tsed/* package to the latest 7.x.
  2. Set useDefineForClassFields: false in every transpiler configuration that exists:
    • tsconfig.json → compilerOptions.useDefineForClassFields
    • .swcrc and SWC options in vite.config.ts / vitest.config.ts → jsc.transform.useDefineForClassFields
    • Keep legacyDecorator: true and decoratorMetadata: true (SWC), experimentalDecorators and emitDecoratorMetadata (tsc).
  3. Replace proxy access on the configuration object. v8 removes it:
ts
import {Configuration, Injectable} from "@tsed/di";

@Injectable()
export class MyService {
  constructor(@Configuration() private settings: Configuration) {
    settings.get<string>("myOption"); // v7 and v8
    // settings.myOption             // v7 only, undefined in v8
  }
}
  1. Find candidates: search for settings., configuration. and this.settings. followed by a custom key. Built-in accessors (rootDir, env, imports, routes, mount, logger, debug, version) keep working; anything else must use .get("key"), constant("key") or @Constant("key").

3. Prepare on v7: switch to ESM

  1. package.json: set "type": "module".
  2. tsconfig.json: "module": "NodeNext", "moduleResolution": "NodeNext", "target": "esnext".
  3. Add .js to every relative import and export, and /index.js to directory imports:
ts
import {ProductsService} from "./services/ProductsService.js";
import * as rest from "./controllers/rest/index.js";
  1. Fix deep CommonJS imports (lodash/get → lodash/get.js) and named imports from CommonJS-only packages (import fs from "fs-extra").
  2. Replace __dirname / __filename with import.meta.dirname / import.meta.filename, and require() with import.
  3. JSON: import config from "./config.json" with {type: "json"}, or read the file with node:fs.
  4. Replace barrelsby with @tsed/barrels (binary barrels, configuration .barrels.json); the barrelsby configuration format is accepted.
  5. Replace ts-node / ts-node-dev with SWC: install @swc-node/register @swc/core @swc/helpers, run with node --import @swc-node/register/esm-register src/index.ts, and add nodemon for watch mode. Details: https://tsed.dev/introduction/migrate-from-v7.md.

Do not mix require and import to work around a failing import; fix the import form.

4. Verify on v7

sh
npx tsc --noEmit
grep -rnE "from \"\.{1,2}/[^\"]*\"" src | grep -vE "\.(js|json)\""   # must print nothing
npm test
npm start    # boot, hit one route, stop

Stop and fix before continuing. A failure here is not a v8 problem.

5. Bump to v8

  1. Set every @tsed/* runtime package to the same 8.x version. Do not align @tsed/logger*, @tsed/barrels or @tsed/cli*; they are versioned separately.
  2. Install and boot. @tsed/common 8.x still exists as a compatibility barrel, so the application should start before step 6.
  3. Apply the v8 behaviour changes:
    • Request logging is no longer automatic. Add import "@tsed/platform-log-request"; in Server.ts and set logger: {logRequest: true}. PlatformLogMiddleware from @tsed/platform-log-middleware is deprecated.
    • View engines must be imported explicitly, for example import "@tsed/engines/PugEngine.js";.
    • Configurable, Enumerable, Writable and the @tsed/core versions of ReadOnly and Deprecated are removed.
    • Hooks moved to @tsed/hooks ($on, $asyncEmit, $alter, $asyncAlter).
  4. Re-run section 4 commands.

6. Remove @tsed/common

  1. List usages: grep -rn "@tsed/common" src test.
  2. Rewrite each import with the symbol table. Typical split:
ts
// before: import {BodyParams, Controller, Post, Req, UseBefore, PlatformTest} from "@tsed/common";
import {Controller} from "@tsed/di";
import {Req} from "@tsed/platform-http";
import {UseBefore} from "@tsed/platform-middlewares";
import {BodyParams} from "@tsed/platform-params";
import {Post} from "@tsed/schema";
// tests only
import {PlatformTest} from "@tsed/platform-http/testing";
  1. Add each owning package to dependencies, then remove @tsed/common.
  2. @tsed/common imported @tsed/logger-file as a side effect. If file appenders are used, add import "@tsed/logger-file"; explicitly.
  3. Resolve remaining deprecations with the replacement table. Adopt the functional DI API only where it simplifies code; decorators remain supported. See the tsed-di skill.

Do not import PlatformTest from @tsed/platform-http in application code; it lives in @tsed/platform-http/testing.

Show full SKILL.md (345 more words)Show less

7. Tests: Jest to Vitest

Jest is unstable with ESM. Migrate when the suite fails after section 3.

  1. Install vitest unplugin-swc @swc/core @vitest/coverage-v8; create vitest.config.ts from https://tsed.dev/tutorials/vitest.md (SWC plugin with useDefineForClassFields: false).
  2. Replace jest.fn, jest.spyOn, jest.mock with vi.fn, vi.spyOn, vi.mock (import vi from vitest unless globals: true).
  3. Replace PlatformTest.inject([...], fn) with PlatformTest.invoke(Token) or PlatformTest.get(Token).
  4. Use the tsed-testing skill for test structure and the tsed-cli skill to add @tsed/cli-plugin-vitest.

8. Plain Express application

  1. Move the legacy code to src/legacy/ and make sure src/index.ts does not exist.
  2. Scaffold over the existing package.json with the tsed-cli skill (tsed init ., platform express); rename conflicting scripts first.
  3. Export the legacy express.Router() and mount it in @Configuration: middlewares: [{use: expressRouter, hook: "$beforeRoutesInit"}], so existing routes keep working.
  4. In legacy handlers, reach Ts.ED services with inject(MyService) from @tsed/di.
  5. Port routes to controllers incrementally (tsed-controllers, tsed-middlewares). Guide: https://tsed.dev/introduction/migrate-from-express.md.

Pitfalls

  • Injected properties are undefined in constructors or at runtime: useDefineForClassFields is still true in one of tsconfig.json, .swcrc, vite.config.ts, vitest.config.ts.
  • ERR_MODULE_NOT_FOUND on a relative path: missing .js extension or a directory import without /index.js.
  • ERR_REQUIRE_ESM: a CommonJS entry point or loader (ts-node, --require) is still in use. Use --import.
  • Module '"@tsed/common"' has no exported member 'Returns' (or Property, Required): in v8 the barrel re-exports only the routing decorators of @tsed/schema. Import from @tsed/schema.
  • Request logs disappeared after the bump: @tsed/platform-log-request is not imported.
  • The migration guide shows import ... from "./config.json.js" assert {type: "json"} and @swc-node/register/register-esm. Use ./config.json with with {type: "json"} and @swc-node/register/esm-register.
  • Controllers discovered through barrels silently vanish when barrels is not run before start. Keep "barrels": "barrels" in the start script chain.

Checklist

  • Sections 2 to 4 verified on v7 before the v8 bump.
  • "type": "module", NodeNext, .js extensions everywhere, no require, no __dirname.
  • useDefineForClassFields: false in every transpiler configuration.
  • No custom key read through settings.<key>.
  • All @tsed/* runtime packages on the same 8.x version; @tsed/common removed and no import of it left.
  • @tsed/platform-log-request and view engines imported explicitly where needed.
  • npx tsc --noEmit, the test suite and a manual boot all pass.

© tsedio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in plugins/tsed/skills/tsed-migration of tsedio/tsed.

  • SKILL.md
  • agents/openai.yaml
  • references/common-symbols.md
  • references/deprecated-apis.md

Open the folder on GitHubat commit cebcc11

Compare with similar skills

Tsed Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tsed Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tsed Migration this skilltsedio/tsed3.1k—~2.5kAutomated safety check: PassMIT
Test Detectdavila7/claude-code-templates32k—~989Automated safety check: PassMIT
Vitestsupabase/supabase111k12 repos~1.1kAutomated safety check: PassApache-2.0
Test GuardamElnagdy/guard-skills1.3k2 repos~2.1kAutomated safety check: PassMIT
Vitestpixel-point/animate-text1492 repos~1.3kAutomated safety check: PassNone
Designing TestsCloudAI-X/claude-workflow-v21.4k1 repos~1.5kAutomated safety check: PassMIT

Similar skills

  • Test Detect

    davila7/claude-code-templates

    Auto-detect testing framework and run relevant tests. An agent skill from davila7/claude-code-templates.

    32k GitHub stars~989 tokensUpdated today
    Testing & QAAuto-check passed
  • Vitest

    supabase/supabase

    Official

    Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.

    111k GitHub starsUsed in 12 repos~1.1k tokens
    Testing & QAAuto-check passed
  • Test Guard

    amElnagdy/guard-skills

    Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.

    1.3k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed
  • Vitest

    pixel-point/animate-text

    Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest).

    149 GitHub starsUsed in 2 repos~1.3k tokens
    Testing & QAAuto-check passed
  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-check passed
  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

More from tsedio/tsed

All 19 skills in this repo
  • Create a production-ready Ts.ED platform adapter for a new HTTP framework or runtime, such as Hono, Elysia, Bun.serve, or a Node framework.

    3.1k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Tsed CLI

    tsedio/tsed

    Scaffolds Ts.ED v8 projects and generates files with the Ts.ED CLI v7, through its MCP server (tools set-workspace, init-project, list-templates, get-template, generate-file) or the tsed binary…

    3.1k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Configure and bootstrap a Ts.ED v8 server - the @Configuration decorator or configuration() on the Server class, PlatformExpress/PlatformKoa/PlatformFastify.bootstrap, server options (mount…

    3.1k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check: notes
  • Tsed Di

    tsedio/tsed

    Declare, inject and scope Ts.ED v8 providers and wire lifecycle hooks - @Injectable, @Module, @Controller, @Inject, the functional API (inject, injectMany, lazyInject, constant, refValue…

    3.1k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Tsed Docs

    tsedio/tsed

    Locates authoritative Ts.ED v8 documentation and API reference instead of guessing framework APIs.

    3.1k GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Tsed Logger

    tsedio/tsed

    Configure and use logging in a Ts.ED v8 application with @tsed/logger v8.

    3.1k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Tsed Migration

What does Tsed Migration do?

Migrates an application to Ts.ED v8 from v7, with pointers for v6 and plain Express apps. Tsed Migration is an agent skill from tsedio/tsed.ED v8 from v7, with pointers for v6 and plain Express apps.

When should I use Tsed Migration?

Tsed Migration fits situations like: package.json has @tsed/ 6.x; on ERRREQUIREESM; ERRMODULENOTFOUND; has no exported member from @tsed/common.

How do I install Tsed Migration in Claude Code?

Run `npx skills add tsedio/tsed --skill tsed-migration -a claude-code`. Or copy the skill folder (plugins/tsed/skills/tsed-migration in tsedio/tsed) into .claude/skills/tsed-migration in your project. Claude Code loads it when a task matches its description.

How do I install Tsed Migration in Codex?

Run `npx skills add tsedio/tsed --skill tsed-migration -a codex`. Or copy the skill folder (plugins/tsed/skills/tsed-migration in tsedio/tsed) into .agents/skills/tsed-migration in your project. Codex loads it when a task matches its description.

Can I use Tsed Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tsedio/tsed --skill tsed-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tsed-migration, .gemini/skills/tsed-migration, .github/skills/tsed-migration and .opencode/skills/tsed-migration in your project.

What does Tsed Migration need to run?

Going by SKILL.md and its folder, Tsed Migration needs the command-line tools its instructions call (npx, npm, node and vitest). Our summary lists: Node.js.

Does Tsed Migration access the network?

SKILL.md names 1 domain. In commands or code: tsed.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Tsed Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tsed Migration use?

Tsed Migration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tsed Migration use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Tsed Migration?

Skills that share tags, products or a category with Tsed Migration: Test Detect (davila7/claude-code-templates, 32k stars), Vitest (supabase/supabase, 111k stars), Test Guard (amElnagdy/guard-skills, 1.3k stars) and Vitest (pixel-point/animate-text, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tsed Migration?

tsedio (a GitHub organization) maintains it in tsedio/tsed, which has 3,088 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

Source: tsedio/tsed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.