@tsrx/mcp 0.0.81 → 0.0.82

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
@@ -3,7 +3,7 @@
3
3
  "description": "MCP server for TSRX documentation and project context",
4
4
  "license": "MIT",
5
5
  "author": "Dominic Gannaway",
6
- "version": "0.0.81",
6
+ "version": "0.0.82",
7
7
  "type": "module",
8
8
  "repository": {
9
9
  "type": "git",
@@ -37,8 +37,8 @@
37
37
  "@modelcontextprotocol/sdk": "^1.29.0",
38
38
  "prettier": "^3.9.6",
39
39
  "zod": "^4.3.6",
40
- "@tsrx/core": "0.1.58",
41
- "@tsrx/prettier-plugin": "0.3.120"
40
+ "@tsrx/core": "0.1.59",
41
+ "@tsrx/prettier-plugin": "0.3.121"
42
42
  },
43
43
  "devDependencies": {
44
44
  "@types/node": "^24.3.0",
@@ -72,9 +72,9 @@ export const documentation_sections = [
72
72
  slug: 'target-integration',
73
73
  title: 'Target Integration',
74
74
  use_cases:
75
- 'runtime target, compiler package, target-specific setup, skills, runtime semantics',
75
+ 'runtime target, compiler package, target-specific setup, runtimeImports, direct runtime dependency, skills, runtime semantics',
76
76
  content:
77
- '# Target Integration\n\nTSRX authoring syntax is shared, but output and runtime semantics are target-defined.\n\nThe core MCP server should detect the target, then hand off runtime-specific questions to a target-specific skill, prompt, resource set, or compiler-backed tool.\n\nTarget-specific layers should own:\n- package installation and bundler setup\n- runtime imports and helper APIs\n- compiler warnings and semantic restrictions\n- examples that depend on a specific rendering runtime\n\nWhen helping in an existing project, detect the target before generating code. If no target-specific layer is available, stay within target-neutral TSRX syntax and ask for confirmation before assuming runtime APIs.\n\nSource: website-tsrx/src/pages/getting-started.tsrx',
77
+ "# Target Integration\n\nTSRX authoring syntax is shared, but output and runtime semantics are target-defined.\n\nThe core MCP server should detect the target, then hand off runtime-specific questions to a target-specific skill, prompt, resource set, or compiler-backed tool.\n\nTarget-specific layers should own:\n- package installation and bundler setup\n- runtime imports and helper APIs\n- compiler warnings and semantic restrictions\n- examples that depend on a specific rendering runtime\n\nCompiler-package helper imports are the default. If a target compiler or build integration uses `runtimeImports: 'direct'`, the package that owns the source or generated modules must declare the matching standalone runtime as a direct production dependency:\n\n- React: `@tsrx/react-runtime`\n- Preact: `@tsrx/preact-runtime`\n- Solid: `@tsrx/solid-runtime`\n- Vue: `@tsrx/vue-runtime`\n\nBuild tools may bundle these helpers or leave their bare imports external, but they do not provide the runtime package. It must be resolvable during the build; do not rely on hoisting or on a compiler's transitive dependency.\n\nWhen helping in an existing project, detect the target before generating code. If no target-specific layer is available, stay within target-neutral TSRX syntax and ask for confirmation before assuming runtime APIs.\n\nSource: website-tsrx/src/pages/getting-started.tsrx#direct-runtime-imports",
78
78
  },
79
79
  {
80
80
  slug: 'tooling',