@tsrx/mcp 0.0.9 → 0.0.11

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.9",
6
+ "version": "0.0.11",
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.8.3",
39
39
  "zod": "^4.3.6",
40
- "@tsrx/core": "0.0.27",
41
- "@tsrx/prettier-plugin": "0.3.48"
40
+ "@tsrx/core": "0.1.0",
41
+ "@tsrx/prettier-plugin": "1.0.0"
42
42
  },
43
43
  "devDependencies": {
44
44
  "@types/node": "^24.3.0",
@@ -11,7 +11,7 @@ export const documentation_sections = [
11
11
  use_cases:
12
12
  'always, introduction, explain tsrx, compare jsx, language model context, runtime targets',
13
13
  content:
14
- '# TSRX Overview\n\nTSRX is a TypeScript language extension for authoring declarative UI in .tsrx files. It adds a small set of syntax forms on top of TypeScript, while letting each target compiler define the runtime semantics.\n\nCore ideas:\n- component declarations use the component keyword.\n- JSX-like elements can be written as statements inside component bodies.\n- control-flow statements can contain template output.\n- expression-position JSX must use <>...</> or <tsx>...</tsx>.\n- lazy destructuring uses &[] and &{} for by-reference bindings.\n\nThe core language docs should stay target-neutral. After identifying the active runtime target, use target-specific docs, prompts, or skills for runtime imports, bundler setup, and semantics that are not defined by TSRX itself.\n\nSource: website-tsrx/src/pages/specification.tsrx',
14
+ '# TSRX Overview\n\nTSRX is a TypeScript language extension for authoring declarative UI in .tsrx files. It adds a small set of syntax forms on top of TypeScript, while letting each target compiler define the runtime semantics.\n\nCore ideas:\n- component declarations use the component keyword.\n- JSX-like elements can be written as statements inside component bodies.\n- control-flow statements can contain template output.\n- expression-position native TSRX must use <tsrx>...</tsrx>; JSX-style values use <>...</> or <tsx>...</tsx>.\n- lazy destructuring uses &[] and &{} for by-reference bindings.\n\nThe core language docs should stay target-neutral. After identifying the active runtime target, use target-specific docs, prompts, or skills for runtime imports, bundler setup, and semantics that are not defined by TSRX itself.\n\nSource: website-tsrx/src/pages/specification.tsrx',
15
15
  },
16
16
  {
17
17
  slug: 'components',
@@ -31,11 +31,11 @@ export const documentation_sections = [
31
31
  },
32
32
  {
33
33
  slug: 'tsx-expression-values',
34
- title: 'TSX Expression Values',
34
+ title: 'Expression Values',
35
35
  use_cases:
36
- 'fragments, tsx tag, pass jsx as prop, return jsx from helper, expression position jsx',
36
+ 'fragments, tsrx tag, tsx tag, pass template as prop, return template from helper, render props, expression position jsx',
37
37
  content:
38
- '# TSX Expression Values\n\nRegular template elements in component bodies are statements and have no value. When JSX must be used in expression position, wrap it in `<>...</>` or `<tsx>...</tsx>`.\n\n```tsx\ncomponent App() {\n const title = <><span>"Settings"</span></>;\n\n <Card title={title} />\n}\n```\n\nUse this for assigning JSX to variables, returning JSX from helper functions, or passing JSX as props. Do not write `const el = <div />` directly in TSRX component code.\n\nSpecification grammar:\n\n```text\nTsxElement :\n <tsx> TsxChildrenopt </tsx>\n\nTsxCompatElement :\n <tsx: IdentifierName> TsxChildrenopt </tsx: IdentifierName>\n\nTsxFragmentShorthand :\n <> TsxChildrenopt </>\n```\n\nSource: website-tsrx/src/pages/specification.tsrx#tsx-islands',
38
+ '# Expression Values\n\nRegular template elements in component bodies are statements and have no value. When native TSRX must be used in expression position, wrap it in `<tsrx>...</tsrx>`. When JSX-style children must be used in expression position, wrap them in `<>...</>` or `<tsx>...</tsx>`.\n\n```tsx\ncomponent App() {\n const title = <tsrx><span>"Settings"</span></tsrx>;\n\n <Card title={title} />\n}\n```\n\nNative TSRX expression fragments can contain setup statements and template control flow:\n\n```tsx\nfunction badge(label: string) {\n return <tsrx>\n const normalized = label.trim();\n <span class="badge">{normalized}</span>\n </tsrx>;\n}\n```\n\nUse these wrappers for assigning UI to variables, returning UI from helper functions, or passing UI as props. Do not write `const el = <div />` directly in TSRX component code.\n\nSpecification grammar:\n\n```text\nTsrxExpression :\n <tsrx> TemplateChildrenopt </tsrx>\n\nTsxElement :\n <tsx> TsxChildrenopt </tsx>\n\nTsxCompatElement :\n <tsx: IdentifierName> TsxChildrenopt </tsx: IdentifierName>\n\nTsxFragmentShorthand :\n <> TsxChildrenopt </>\n```\n\nSource: website-tsrx/src/pages/specification.tsrx#tsx-islands',
39
39
  },
40
40
  {
41
41
  slug: 'control-flow',